Execute stack after cloudFormation Deploy
up vote
0
down vote
favorite
I have a ApiGateway made with Serverless-model-application that I made a integration with GitHub via CodePipeline, everything is running fine, the pipeline reads the webhook, builds the buildpsec.yml and deploys the CloudFormation file, creating the updating the stack.
The thing is after the stack is updated it still needs a approval on the console, how can I make the execute on the stack update be auto-run?
amazon-web-services
add a comment |
up vote
0
down vote
favorite
I have a ApiGateway made with Serverless-model-application that I made a integration with GitHub via CodePipeline, everything is running fine, the pipeline reads the webhook, builds the buildpsec.yml and deploys the CloudFormation file, creating the updating the stack.
The thing is after the stack is updated it still needs a approval on the console, how can I make the execute on the stack update be auto-run?
amazon-web-services
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a ApiGateway made with Serverless-model-application that I made a integration with GitHub via CodePipeline, everything is running fine, the pipeline reads the webhook, builds the buildpsec.yml and deploys the CloudFormation file, creating the updating the stack.
The thing is after the stack is updated it still needs a approval on the console, how can I make the execute on the stack update be auto-run?
amazon-web-services
I have a ApiGateway made with Serverless-model-application that I made a integration with GitHub via CodePipeline, everything is running fine, the pipeline reads the webhook, builds the buildpsec.yml and deploys the CloudFormation file, creating the updating the stack.
The thing is after the stack is updated it still needs a approval on the console, how can I make the execute on the stack update be auto-run?
amazon-web-services
amazon-web-services
edited Nov 8 at 23:18
Angel Oropeza
10514
10514
asked Nov 8 at 19:38
Daniel Bezerra De Menezes
389418
389418
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
It sounds like your pipeline is doing one of two things, unless I'm misunderstanding you:
- Making a change set but not executing it in the cloudformation console.
- Proceeding to a manual approval step in the pipeline and awaiting your confirmation.
Since #2 is simply solved by removing that step, let's talk about #1.
Assuming you are successfully creating a change set called ChangeSetName, you need a step in your pipeline with the following (cfn JSON template syntax):
"Name": "StepName",
"ActionTypeId": {"Category": "Deploy",
"Owner": "AWS",
"Provider": "CloudFormation",
"Version": "1"
},
"Configuration": {
"ActionMode": "CHANGE_SET_EXECUTE",
"ChangeSetName": {
"Ref": "ChangeSetName"
},
...
Keep the other parameters (e.g. RoleArn) consistent per usual.
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
1
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It sounds like your pipeline is doing one of two things, unless I'm misunderstanding you:
- Making a change set but not executing it in the cloudformation console.
- Proceeding to a manual approval step in the pipeline and awaiting your confirmation.
Since #2 is simply solved by removing that step, let's talk about #1.
Assuming you are successfully creating a change set called ChangeSetName, you need a step in your pipeline with the following (cfn JSON template syntax):
"Name": "StepName",
"ActionTypeId": {"Category": "Deploy",
"Owner": "AWS",
"Provider": "CloudFormation",
"Version": "1"
},
"Configuration": {
"ActionMode": "CHANGE_SET_EXECUTE",
"ChangeSetName": {
"Ref": "ChangeSetName"
},
...
Keep the other parameters (e.g. RoleArn) consistent per usual.
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
1
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
add a comment |
up vote
1
down vote
accepted
It sounds like your pipeline is doing one of two things, unless I'm misunderstanding you:
- Making a change set but not executing it in the cloudformation console.
- Proceeding to a manual approval step in the pipeline and awaiting your confirmation.
Since #2 is simply solved by removing that step, let's talk about #1.
Assuming you are successfully creating a change set called ChangeSetName, you need a step in your pipeline with the following (cfn JSON template syntax):
"Name": "StepName",
"ActionTypeId": {"Category": "Deploy",
"Owner": "AWS",
"Provider": "CloudFormation",
"Version": "1"
},
"Configuration": {
"ActionMode": "CHANGE_SET_EXECUTE",
"ChangeSetName": {
"Ref": "ChangeSetName"
},
...
Keep the other parameters (e.g. RoleArn) consistent per usual.
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
1
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It sounds like your pipeline is doing one of two things, unless I'm misunderstanding you:
- Making a change set but not executing it in the cloudformation console.
- Proceeding to a manual approval step in the pipeline and awaiting your confirmation.
Since #2 is simply solved by removing that step, let's talk about #1.
Assuming you are successfully creating a change set called ChangeSetName, you need a step in your pipeline with the following (cfn JSON template syntax):
"Name": "StepName",
"ActionTypeId": {"Category": "Deploy",
"Owner": "AWS",
"Provider": "CloudFormation",
"Version": "1"
},
"Configuration": {
"ActionMode": "CHANGE_SET_EXECUTE",
"ChangeSetName": {
"Ref": "ChangeSetName"
},
...
Keep the other parameters (e.g. RoleArn) consistent per usual.
It sounds like your pipeline is doing one of two things, unless I'm misunderstanding you:
- Making a change set but not executing it in the cloudformation console.
- Proceeding to a manual approval step in the pipeline and awaiting your confirmation.
Since #2 is simply solved by removing that step, let's talk about #1.
Assuming you are successfully creating a change set called ChangeSetName, you need a step in your pipeline with the following (cfn JSON template syntax):
"Name": "StepName",
"ActionTypeId": {"Category": "Deploy",
"Owner": "AWS",
"Provider": "CloudFormation",
"Version": "1"
},
"Configuration": {
"ActionMode": "CHANGE_SET_EXECUTE",
"ChangeSetName": {
"Ref": "ChangeSetName"
},
...
Keep the other parameters (e.g. RoleArn) consistent per usual.
answered Nov 8 at 23:20
Charles Landau
1,0851111
1,0851111
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
1
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
add a comment |
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
1
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Thanks dude, u got it right
– Daniel Bezerra De Menezes
Nov 9 at 11:38
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
Which one was it @DanielBezerraDeMenezes ?
– Charles Landau
Nov 9 at 13:02
1
1
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
The first one, i added an extra step in the pipeline with the change set execute.
– Daniel Bezerra De Menezes
Nov 9 at 13:06
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53214964%2fexecute-stack-after-cloudformation-deploy%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown