-
Notifications
You must be signed in to change notification settings - Fork 79
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
feat(api): allow ${env} reference in custom-roles.json #804
feat(api): allow ${env} reference in custom-roles.json #804
Conversation
Hey @joekiller overall looks good, could you undo your changes to the yarn.lock? We'll manage yarn.lock changes separately |
f54309e
to
d11e788
Compare
@marcvberg I have removed the yarn.lock changes |
@marcvberg anything else I can do here? this feature would be useful for my team already :) |
@marcvberg, @sundersc, or @alharris-at seems the docs have shipped but this has yet to merge. |
Hi @joekiller, just committed an additional merge conflict change, and reviewing this PR now. Also kicking off e2e tests, if those all look good, we'll get this merged in. Thank you for following up. |
Description of changes
Allow using
${env}
in custom-roles.json to reference the current Amplify CLI environment.Also lint --fix was applied.
Issue #, if available
Documentation update: aws-amplify/docs#4591
Description of how you validated changes
Added tests.
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.