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
{{ message }}
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
Unfortunately this is also hard coded in the lambda:
const MASTER_ROLE_PATH = '/gorillastack/autotag/master/';
class AutotagDefaultWorker {
...
It would be great if the role path could be passed into the lambda. This would make CFN the only source of truth and thereby not require to rebuild the lambda.
The text was updated successfully, but these errors were encountered:
Roles are tricky, they're named after the STACK's id automatically by CF and they ALREADY have a limit that's almost reached. If you add more stuff to that string you might end up breaking the CF deployment because of the resource(in this case IAM role) limit. I've seen this happen in other projects.
I'm working in an environment where we use naming conventions to indicate ownership (in addition to tagging).
Would love the ability to prefix autotag's role paths like so:
Unfortunately this is also hard coded in the lambda:
It would be great if the role path could be passed into the lambda. This would make CFN the only source of truth and thereby not require to rebuild the lambda.
The text was updated successfully, but these errors were encountered: