You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In this example, I know the destination environment from $BITBUCKET_BRANCH in my step set-deployment-environment. I set my environment variable $ENV_NAME, but deployment will not accept an environment variable as I believe this needs to be a string.
- step: *set-deployment-environment
name: Deploying to environment
Can anyone suggest a solution?
Hello @Mach Dinh-Vu ,
Thank you for reaching out to Atlassian Community!
Unfortunately, it's currently not possible to define a dynamic environment in the YML file using environment variables. The deployment environment of the step needs to be a fixed static value that was previously created under the Deployments section of Repository Settings. We do have an open feature request to implement the ability for deployment environments to be configured dynamically/using env variable, which you can find below :
I would suggest you to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.
Thank you, @Mach Dinh-Vu !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.