Performing a change-set in one job and executing it in another

DevOps AWS
#1

We are using AWS SAM and Gitlab CI/CD. I was wondering how to perform a change-set in one job and execute it in another one.

#2

What problem are you running into?

#3

I don’t know how to execute the change-set created in job A, in job B

#4

I first want to see the changes

#5

Doing that in another job would result in rebuilding the lambdas (using cache), regenerate the package.yml file etc

#6

When you create the change set, it emits a change set id, then you call execute_change_set against that stack and change set id

#7

I do the same thing in GH Action

#8

You grab the change set id via regex ?

#9

Changeset created successfully. arn:aws:cloudformation:eu-central-1:****:changeSet/samcli-deploy1641481030/a4957719-f1a7-4e49-b5b4-9f2dd6d12996

#10

Oh I’m sorry I missed the SAM part of your question

#11

I could use SAM to build and CF cli to create the changeset

#12

Yeah, that’s what I do

#13

SAM does have a “confirm” option in deploy, but it’s designed for the console

#14

Could create a slack notification with manual step and all but a bit overkilled

#15

How do you pass the change set id? In Gitlab, it doesn’t seem easy

#16

I found all the existing tools very weak in this specific area (being able to post a change set and wait for approval before continuing), so I wrote my own github custom action which is basically just a thin wrapper around create/execute_change set

#17

Though in theory you could do it even with cli

#18

The reason I went for a tool was managing different parameters for environments

#19

Thanks for your input!

#20

No problem, good luck