-
Notifications
You must be signed in to change notification settings - Fork 18
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: extend AWS policy #187
Conversation
Great work on the spec side so far! Let me know if you need help on the implementation side 👍 |
Thank you! I've just pushed some changes to align with the recent spec changes. Would appreciate a review and any feedback 🙏 |
Only have a few minor things, otherwise its looking great! |
@Gadam8 looks great in its current iteration. |
Thank you! Yeah I'm happy with how these changes look 👍 Happy to proceed |
Thanks for the merge @VisualBean! What's the process for releasing a new version? Is it possible to get a beta release now? Thanks 👍 |
Yeah ill rebase it to the vnext branch and release a new beta nuget (probably before end of day today). Edit: Ive pushed a beta release with the new binding changes. |
About the PR
The current AWS policy binding configuration doesn't match what is offered by AWS when configuring IAM policies. Condition and Resource are missing and Principal isn't fully fleshed out. e.g. https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html#Condition-multiple-conditions & https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html. This PR addresses this by extending the binding configuration for SNS and SQS.
See related JSON bindings PR here - asyncapi/spec-json-schemas#553
Changelog
Related Issues
N/A