You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've run into a problem when it comes to CodePipeline notifications, and it seems that your code (codepipeline-notifications.yml) is experiencing the same problem. If you can, please verify that your template isn't working as expected.
Steps to reproduce:
Run aws cloudformation create-stack --stack-name Notifications --template-body file://codepipeline-notifications.yml --parameter ParameterKey=EmailAddress,ParameterValue=<your email> and wait for stack to be created
Accept the subscription confirmation by clicking the link in the received e-mail
Trigger a CodePipeline that is configured to fail and wait for it to complete
Verify that you haven't received an e-mail, but at this point you ought to have
Navigate to CloudWatch and edit your rule. Don't change anything, just click through the wizard and update the rule in the console.
Trigger the pipeline again. This time you will receive an e-mail.
As I said, I don't think anything is wrong in your template. I'm experiencing the same issue with one of my templates. But it would be beneficial if your sample indicated that the template didn't behave as expected, given you are able to reproduce the issue.
Best regards,
Mattias
The text was updated successfully, but these errors were encountered:
Request
Details
I've run into a problem when it comes to CodePipeline notifications, and it seems that your code (
codepipeline-notifications.yml
) is experiencing the same problem. If you can, please verify that your template isn't working as expected.Steps to reproduce:
aws cloudformation create-stack --stack-name Notifications --template-body file://codepipeline-notifications.yml --parameter ParameterKey=EmailAddress,ParameterValue=<your email>
and wait for stack to be createdAs I said, I don't think anything is wrong in your template. I'm experiencing the same issue with one of my templates. But it would be beneficial if your sample indicated that the template didn't behave as expected, given you are able to reproduce the issue.
Best regards,
Mattias
The text was updated successfully, but these errors were encountered: