Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,127
Community Members
 
Community Events
168
Community Groups

YAML anchors + Overriding + Reusing deployment variables

Edited

So here is a doozy

  1. For some reason bitbucket does not allow us to use the deployment variables for more than on step.
  2. To get around this we are passing in variables through the use of artifacts to the next step.
  3. As one of those variables is an AWS Key we obviously don't want to pass that off as an artifact to leave out in the open.
  4. To get around this we are creating a separate AWS variable at the repo level for each environment.

The problem is if you are reusing steps vs YAML anchors (say s3 deploy pipe), how would you get the right AWS variable to be called in the reused pipes? Sample code below. So say I have different keys for Dev and UAT

definitions:
- step: &build-and-deploy
name: Build And Deploy
script:
- pipe: atlassian/aws-s3-deploy:0.2.4
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
pipelines:
branches:
dev:
- step: *build-and-deploy
uat:
- step: *build-and-deploy

 

 

 

2 answers

@Ming Han Chung I have the same issue. I want to reuse codedeploy pipe and replace the value of DEPLOYMENT_GROUP.

 master:
- step: *build
- step:
<<: *deploy
name: Deploy to Prod
deployment: production
trigger: manual
script:
variables:
DEPLOYMENT_GROUP: 'production-deployment-group'

@Abryan Manalansang  did you get a solution to this?

likewise! This would save me a lot of effort

did this work for you?

There a possible hacky solution here: https://community.atlassian.com/t5/Bitbucket-questions/Bitbucket-Pipeline-Using-a-different-environmental-variable/qaq-p/1023246

Basically use a step that writes env vars to a file and pass that around... 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,487 views 3 10
Read article

Atlassian Community Events