What is the right way to add a 'LABELS' array with more than one entry in https://bitbucket.org/atlassian/aws-eks-kubectl-run/src/master/ pipe?
It fails with the following syntax:
---
LABELS:
- "{'bitbucket.org/bitbucket_tag':\"$BITBUCKET_TAG\"}"
- "{'bitbucket.org/bitbucket_build_number':\"$BITBUCKET_BUILD_NUMBER\"}"
- "{'bitbucket.org/bitbucket_commit':\"$BITBUCKET_COMMIT\"}"
---
Hi @Saurabh Singh @Brad Vrabete
Thank you for your question!
Yep, there was a bug in the pipe with LABELS array and now it is fixed.
A new version of the aws-eks-kubectl-run pipe released:
script: - pipe: atlassian/aws-eks-kubectl-run:1.4.1 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION CLUSTER_NAME: 'my-kube-cluster' KUBECTL_COMMAND: 'apply' RESOURCE_PATH: 'nginx.yml' LABELS: - 'environment=production' - 'tier=backend'
LABELS:
Key=value pairs that are attached to a Deployment. Labels are intended to be used to specify identifying attributes of objects. Valid labels must follow Syntax and character set. Format:key=value
. Example:bitbucket.org/bitbucket_branch=develop
.
It would be nice if you provide us with more details about your experience with the aws-eks-kubectl-run pipe.
Cheers,
Oleksandr
@Oleksandr Kyrdan Indeed that change solves the issue; I was able to successfully add labels in the way you have described.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The syntax
- "'bitbucket.org/bitbucket_tag'="$BITBUCKET_TAG\"" does not work either
What is the correct syntax for adding custom labels for this pipe?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.