We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the Configuration section of the README, I see this sentence:
role Role to apply to the warmer lambda (defaults to the role in the provider)
In reality it creates a role that allows lambda:InvokeFunction on the other functions on the stack. Is it an error on the description?
lambda:InvokeFunction
The text was updated successfully, but these errors were encountered:
Hi @nbcchen ,
Can you give me an example YAML or a project to replicate the issue?
The role setting should simply apply this role to the function. If no role is provided, then the default role should be created.
role
Sorry, something went wrong.
@juanjoDiaz in the README it describe the role node as below Role to apply to the warmer lambda (defaults to the role in the provider)
But it does not default to the role in the provider, it instead generates a new role called WarmUpPluginDefaultRole
WarmUpPluginDefaultRole
You are right! This changed in v5 as stated in the documentation. But it seems that one part of the docs was not fixed.
Fixed now 🙂
No branches or pull requests
In the Configuration section of the README, I see this sentence:
In reality it creates a role that allows
lambda:InvokeFunction
on the other functions on the stack. Is it an error on the description?The text was updated successfully, but these errors were encountered: