Skip to content

Conversation

abrucker235
Copy link

Changed it so that consumers could create auth roles based on lambda name and don't have to set additional variable unless they want it to be called different.

@hashicorp-cla
Copy link

hashicorp-cla commented Nov 12, 2020

CLA assistant check
All committers have signed the CLA.

@catsby
Copy link
Contributor

catsby commented Nov 23, 2020

Hey @abrucker235 - thanks for the contribution here! I admit I'm reluctant to merge this however without knowing if this is a common pattern for our users, or if it's particular to your specific usage patterns. I hope that makes sense.

@abrucker235
Copy link
Author

@catsby this might be a pattern we use and I can see the hesitation, but its a pattern I feel helps encourage not reusing vault roles across different lambdas and practice least access. Technically this doesn't turn off the original capability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants