-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Support security
field at Operation level
#434
Comments
Ack. Is simply copying the function ok? Would you in addition like ServerSecurityRequirement (server-security-requirement.js) renamed to 'SecurityRequirement' and reused for both server and operation - or a OperationSecurityRequirement equivalent created? |
@sekharbans-ebay Hi!
as I see |
Thanks so much Lokesh! |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Handled by #505 |
Reason/Context
Part of asyncapi/spec#584.
Description
Support
security
field containing an array of SecurityRequirement at Operation level.As this is a good candidate to be in
v2.3.0
release, the PR should be created from and targeting2022-01-release
branch.As far as I see, the change we need to do is to add a new function called
security
into theoperation
model. I think we can copy the one from theserver
found in https://github.com/asyncapi/parser-js/blob/2022-01-release/lib/models/server.js#L65-L72The text was updated successfully, but these errors were encountered: