Why does pipeline validator not catch pipe names without versions?

[Jason Harrison]

In my bitbucket-pipeline.yaml I had a script with references to atlassian/aws-ecs scripts

script:
  - aws configure set aws_access_key_id $AWS_ACCESS_KEY_ID 
  - aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_KEY 
  - aws configure set default.region $AWS_DEFAULT_REGION 
   - pipe: atlassian/aws-ecr-push-image:1.1.2 

For some reason if, I delete the version of the pipe (`:1.1.2`) I get an error:

"Your pipe name is in an invalid format. Check the name of the pipe and try again."

This is not caught by the Validator for bitbucket-pipelines.yml.

[Halyna Berezovska]

@Jason Harrison we do not support pipes without version tags and latest also. This is the reason why you have it failing

Regards, Galyna

[Jason Harrison]

Perhaps changing the error message to something like:

"Your pipe name is in an invalid format. Check the name of the pipe, including the version, and try again."

[Jonathan Duncan]

Agreed. This threw me off as well.

[roman_rakhmatullov]

Seems bitbucket-pipelines.yml validator doesn't catch this problem, but it is shown only when trying to run. That's a problem of validator I believe.

[Halyna Berezovska]

@Jason Harrison @Jonathan Duncan @roman_rakhmatullov we are reporting this to the appropriate team, thank you for the feedback!