-
-
Notifications
You must be signed in to change notification settings - Fork 54
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 configuration #553
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please move changes to new version
@Gadam8 looks good Don't forget to update information about SNS and SQS here: |
Maybe make it an enum for one of them 😅.
Whatever makes the most sense and is the most ‘true’ to the spec i guess.
|
I've raised a PR to address this here asyncapi/bindings#256 |
@iancooper @dpwdec up! |
✅ |
@iancooper hi! One more day, and I'll merge fyi: @Gadam8 @dpwdec @VisualBean |
🎉 This PR is included in version 6.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
The current AWS policy binding configuration doesn't match what is offered by AWS when configuring IAM policies.
Condition
andResource
are missing andPrincipal
isn't fully fleshed out. This PR addresses this by extending the binding configuration for SNS and SQS.Related issue(s)