nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Missing Environment Variables Error.

Darshan Gerra

Hello,

I have created Environments in deployments namely Development and Production which are using different aws accounts for deployment purposes.

I have added variables in development environment :

and this is my pipeline snippet :

this is giving me error - AWS_ACCESS_KEY_ID variable is missing.
I have tried to add in repository variables and it worked, but my requirement is environment specific since we are using different aws accounts for production and development.

Let me know what I'm missing.

Thanks.

Accepted answers

Daniil Penkin

Hello @Darshan Gerra ,

It looks like the step with AWS pipe is missing deployment: Deployment property. The previous step, in turn, shouldn't have it as it doesn't actually do deploy.

Hope this helps.

Cheers,
Daniil

All comments

Daniil Penkin

Hello @Darshan Gerra ,

It looks like the step with AWS pipe is missing deployment: Deployment property. The previous step, in turn, shouldn't have it as it doesn't actually do deploy.

Hope this helps.

Cheers,
Daniil

Darshan Gerra

Thanks Daniil,

adding deployment: Development in first step works, and i'm getting another error in another step. Require your expertise and help.

Pipeline snippet :

Error :

Daniil Penkin

Same thing: if your variables are defined for a specific environment, they are not visible unless your step is marked as deployment step to that environment. Moreover, you can only define a particular deployment environment once per pipeline. That is, you can't mark two or more steps as deployment steps to the very same environment within one pipeline.

So if the second step you added is meant to do something around the same environment (Development in your case), you need to consolidate two steps into one which would call both pipes in its script.

Hope this makes sense. Let me know if you have any questions.

Cheers,
Daniil

Darshan Gerra

Thanks Daniil,

I have tried to merge steps and it worked. One thing I want to know on this : if I have s3 deployment , lambda deployments, docker images deployment to ec2 using code-deploy in my application, So should I include all these in a single step??

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines

atl-pipelines