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; } } }

Deployment variable is not reflecting in pipelines

Jaisa Ram_crwod9

I am using bitbucket pipeline to deploy using S3 deploy and for invalidation of by using aws-cloudfront-invalidate.

I have declared some variables at repository level and some at deployment environment level.

Here:

DISTRIBUTION_ID is a part deployment variable and during the run pipeline it is throwing error (DISTRIBUTION_ID can be a null) while invalidation pipe.

When I move DISTRIBUTION_ID to repository level variable, it is working.

I am using latest version of both pipes.

Accepted answers

Halyna Berezovska

@Jaisa Ram can you provide the code of your pipeline? To use deployment variables you need to put the keyword to pipeline, sth like as

name: Deploy

deployment: production

BUT be aware that deployment variables overwrites repository ones.

For more details see docs:

https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/

Regards, Galyna

All comments

Halyna Berezovska

@Jaisa Ram can you provide the code of your pipeline? To use deployment variables you need to put the keyword to pipeline, sth like as

name: Deploy

deployment: production

BUT be aware that deployment variables overwrites repository ones.

For more details see docs:

https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/

Regards, Galyna

Jaisa Ram_crwod9

Thanks @Halyna Berezovska , it works after updating deployment keyword

Jaisa Ram_crwod9

Fernando Silva Maransatto

Hi, @Halyna Berezovska
I'm using the same deployment variables that I'm using with the previous pipe (aws-s3-deploy) but It shows me the following errors:

✖ Validation errors:<br>AWS_ACCESS_KEY_ID:- null value not allowed<br>AWS_SECRET_ACCESS_KEY:- null value not allowed
DISTRIBUTION_ID:- null value not allowed

I had the same problem and I tried to fixed it using by moving all the variables to the repository settings.

Shouldn't aws-cloudfront-invalidate accept the deployment variables such as was-s3-deploy does?

The issue now is that it shows me the following error:

ERROR: Error creating a cloudfront invalidation<br><br>✖ Failed to create a cloudfront invalidation: An error occurred (AccessDenied) when calling the CreateInvalidation operation: User: arn:aws:iam::<iam>:user/Bitbucket is not authorized to perform: cloudfront:CreateInvalidation on resource: arn:aws:cloudfront::<iam>:distribution/<distribution_id>

Welcome!

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

Quick Links

Find more posts tagged with

cloud

bitbucket-pipelines

aws