-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.47.0] Template with Cloudwatch Rule Enable/Disable Parameter does not override the status #1948
Comments
You shouldn't need that condition, you should be able to directly !Ref? |
Seems same as #2150 and aws/serverless-application-model#1329 |
Even using only |
FWIW, I have a bash script function workaround. It will remove the lambda CloudWatch Event rule trigger and disable the rule itself for SAM rules with the default serverlessrepo*. names. It should be easy to add parameters / variables to. I can't find an AWS CLI way to just disable a CloudWatch Event in the Lambda so I remove it. https://gist.github.com/jewelsjacobs/2ea1b37dd4db5279d038111e77d9d813 |
Your gist is not available. |
I am trying to deploy a
sam
template that has a Cloudwatch Rule that is supposed to be enabled in prod account but disabled in a sandbox account.sam deploy
Currently, the Cloudwatch Rule is
enabled=true
and when I run thesam-cli
command, it should switch toenable=false
. Instead I am getting the following...🤔 Is there a workaround to pass boolean parameters to my sam deployment process.
Thanks.
The text was updated successfully, but these errors were encountered: