Skip to content
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

[FEATURE] Support for AWS EventBridge Event-Bus #262

Open
2 tasks done
wiljafor1 opened this issue Sep 24, 2024 · 3 comments
Open
2 tasks done

[FEATURE] Support for AWS EventBridge Event-Bus #262

wiljafor1 opened this issue Sep 24, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@wiljafor1
Copy link

Why do we need this improvement?

Currently, async-api lacks support for AWS EventBridge Event-Bus, which prevents teams using EventBridge from fully leveraging async-api to document and describe their event-driven architectures in a standardized way. Adding this support would make async-api more flexible and aligned with modern AWS event-driven architectures.

How will this change help?

By introducing AWS EventBridge Event-Bus as a supported binding, users will be able to describe and document their AWS event-driven architectures using async-api. This would streamline the process of defining event buses, rules, and targets, making it easier to integrate with AWS’s native event service.

Screenshots

(Not applicable for this request, but could be added once implemented.)

How could it be implemented/designed?

The feature could be implemented by extending the existing async-api bindings to include AWS EventBridge. Parameters like the event bus name, event rules, and potential target configurations could be added to the specification, allowing users to define how their EventBridge interacts with their system.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

  • I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue?

Yes I am willing to submit a PR!

@wiljafor1 wiljafor1 added the enhancement New feature or request label Sep 24, 2024
Copy link

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup 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.

@derberg
Copy link
Member

derberg commented Dec 16, 2024

Hey, could you provide some examples on what more or less such binding would contain that is not possible to address with AsyncAPI atm? and what AsyncAPI objects need a binding.

Also pinging the only EventBridge expert that I know @boyney123

@boyney123
Copy link

Makes sense to me, maybe provide some example and we can go from there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants