-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
CDK deploy is not updating the changes to IAM statement policy #3538
Comments
I haven't been able to reproduce your issue with what you've described. I've created the following stack: const table = new Table(this, 'table', {
partitionKey: { name: 'id', type: AttributeType.STRING }
});
const lambda = new Function(this, 'function', {
runtime: Runtime.NODEJS_8_10,
handler: 'index.handler',
code: Code.inline('exports.handler = () => { return cb(null, "test"); }'),
}); Deploying that stack, and then adding
Could you give us additional details about your stack to help understand what's blocking the second deployment? |
Hi, initially when it wasn't working I update the lambda code and the deployment worked fine. i thought that was the work around. But, I've been trying to re-create the same issue since morning and I cant. I'll close the ticket. Thanks for having a look at it. and sorry for wasting your time |
No problem! |
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
What is the current behavior?
If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
I had cdk stack that included, appsync, lambda, dax, dynamo. I updated the stack by granting permission on the table to the lambda
dynamoTable.grantReadWriteData(lambdaFunction);
doing a cdk diff shows the changes
when i do, cdk deploy, i get the
deploying...
message but nothing actually happenscdk deploy should update the iam policy
What is the motivation / use case for changing the behavior or adding this feature?
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
The text was updated successfully, but these errors were encountered: