Dynamic Pipelines & Environments

[Georg Duemlein]

I deployed a sample Dynamic Pipeline into development and staging.

How can I distinguish between these two in the dropdown where I select the dynamic pipeline? They both have the same name.

[Syahrul · Accepted solution]

G'day, @Georg Duemlein 

I believe there's a known bug where if you deploy Dynamic Pipelines providers with identical names, the Dynamic Pipelines selector settings show identical provider names that are currently tracked at:

https://jira.atlassian.com/browse/BCLOUD-23383

The workaround is to change the Dynamic Pipelines provider name for now so you can distinguish between them.

I hope this helps

Regards,
Syahrul

[Radu Cristescu]

In short, the name shown in the Bitbucket repository dropdown is the one that was set in the manifest when the last time `forge deploy` was run for the corresponding environment. Change the name in the manifest, deploy, and the name updates in all installations.

In a CI pipeline, you'd basically run `sed` to do an in-place replacement before you deploy. e.g.

sed -Ei "s/ENVIRONMENT/$BITBUCKET_DEPLOYMENT_ENVIRONMENT/g" manifest.yml

where ENVIRONMENT is a placeholder word that you strategically place in the modules:/bitbucket:dynamicPipelinesProvider:/[]/name: field.