Account level Deployment Environment Definition

[Habib Haider]

Is it possible define the deployment environments and its variables on a account level? We currently have that defined on a repo level but there is a need for us to share them across repos. For example, AWS access and secret key tied to an environment which we are having to repeat on all repos causing us management inconvenience. 

[Daniil Penkin]

Hello @Habib Haider,

Thanks for reaching out.

I'm not an expert particularly with Pipelines, but I believe Team and individual account variables is what you're after. They can be accessed from all repositories that belong to the team or account.

Hope this helps.

Cheers,
Daniil

[Habib Haider]

@Daniil Penkin

Thanks for the quick response. I am aware of the ability to define variables on a team level but that doesn't tie into an deployment environment. Is it possible to do something like below on a team level? 

Team Level:

  Deployment:

    Test:

       AWS_Secret_Key: xyz

     UAT:

        AWS_Secret_Key: abc

     Production:

        AWS_Secret_Key: def

The above can be achieved on a repo level but I want that ability on a team level so that I can reuse it across repos. Hopefully that clarifies my question more.

Thanks! 

[Peter Plewa]

Hi @Habib Haider,

This is currently not possible, we are aware of this and are gathering feedback for adding additional variable levels (project, team) at https://jira.atlassian.com/browse/BCLOUD-14959 I would suggest adding your feedback and watching above issue.

Thanks,

Peter

[Habib Haider]

Thanks Peter for your response. Is there any workaround for the time being?

Is it possible to reuse global/team variable at a deployment variable in a stage? Something similar to:

Team level:

  AWS_Secret_Key_Dev: xyz

  AWS_Secret_Key_Uat: xyz

  AWS_Secret_Key_Prod: xyz

Repo level:

  Deployment:

    Dev:

       AWS_Secret_Key: $AWS_Secret_Key_Dev 

    Uat:

       AWS_Secret_Key: $AWS_Secret_Key_Uat

    Prod:

       AWS_Secret_Key: $AWS_Secret_Key_Prod