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

AWS Cloudformation Pipe Fails to Detect Existing Stack After Version Update

Clayo84

When I switch the cloudformation pipe to a new version it fails to detect that the stack already exists and attempts to create a new stack. The new stack creation fails because the stack already existed in AWS, and subsequently the pipe fails.

For example, I've created several stack using the pipe: atlassian/aws-cloudformation-deploy:0.6.3. If I go back to one of those pipelines and change it to the latest version (0.9.2) it will not detect the existing stack in AWS, attempt to create a new stack, and fail.

Accepted answers

Oleksandr Kyrdan

Hi @Clayo84 ,

Thank you for your question!

We'll investigate this case and notify you.

Best regards,
Oleksandr Kyrdan

All comments

Oleksandr Kyrdan

Hi @Clayo84 ,

Thank you for your question!

We'll investigate this case and notify you.

Best regards,
Oleksandr Kyrdan

Clayo84

Any update?

Halyna Berezovska

@Clayo84we are trying to reproduce your issue and find root cause now.

Could you share your bitbucket pipeline file, that part where you execute cloudformation pipes, both versions?

I just tried to reproduce and did not succeed, hope after your sharing will get the root cause.

Regards, Galyna

Clayo84

@Halyna Berezovska @Oleksandr Kyrdan Certainly! The relevant code is going from this:

- step:          
name: Update Cloudformation stack          
script:            
- pipe: atlassian/aws-cloudformation-deploy:0.6.3              
variables:                  
#WAIT: 'true'                                        
AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}                
AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}                
AWS_DEFAULT_REGION: ${AWS_DEFAULT_REGION}                
CAPABILITIES: ['CAPABILITY_IAM', 'CAPABILITY_NAMED_IAM']                
TEMPLATE: serverless_app.yml                
STACK_NAME: ${BITBUCKET_REPO_SLUG}-cloudformation-${BITBUCKET_BRANCH}    
STACK_PARAMETERS: >                  
[{                    
"ParameterKey": "EnvironmentParam",                    
"ParameterValue": "$BITBUCKET_BRANCH"                  
},{                    
"ParameterKey": "NameStubParam",                    
"ParameterValue": "$BITBUCKET_REPO_SLUG"                  
}]

To this:

 - step:
name: Update Cloudformation stack
script:
- pipe: atlassian/aws-cloudformation-deploy:0.9.2
variables: 
#WAIT: 'true' 
AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}
AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}
AWS_DEFAULT_REGION: ${AWS_DEFAULT_REGION}
CAPABILITIES: ['CAPABILITY_IAM', 'CAPABILITY_NAMED_IAM']
TEMPLATE: serverless_app.yml
STACK_NAME: ${BITBUCKET_REPO_SLUG}-cloudformation-${BITBUCKET_BRANCH}
STACK_PARAMETERS: >
[{
"ParameterKey": "EnvironmentParam",
"ParameterValue": "$BITBUCKET_BRANCH"
},{
"ParameterKey": "NameStubParam",
"ParameterValue": "$BITBUCKET_REPO_SLUG"
}] 
EXTRA_PARAMETERS: >
{
"NotificationARNs": [name-removed-to-protect-the-innocent]
}

Please excuse the formatting, I promise it's properly lined up in the file.

Let me know if you need anything else from me!

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

cloudformation