-
Notifications
You must be signed in to change notification settings - Fork 34
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
Proposal for Add-On Configuration Support in OSS OpAMP Specification #202
Comments
What would this look like in practice in its simplest form? Will we add "config" fields to |
Can you expand on this?
Same here, please provide more details.
What are the parts that are missing? We have certain elements on this (e.g. in |
Description:
The current OpAMP specification provides comprehensive guidelines on handling packages and their downloads. However, it lacks a clear stance on how the packages/add-ons themselves should be configured. This feature request proposes the inclusion of a standardized approach for add-on configuration within the specification.
Rationale:
Lack of Knowledge by Main Agent: The main agent may not possess detailed knowledge about the customer-implemented add-ons.
Independent Add-On Lifecycle: Add-ons may have a lifecycle that operates independently of the main agent. Allowing add-ons to be configured separately ensures that their lifecycle can be managed without unnecessary intervention from the main agent.
Counterarguments
Proposal/Ask
Incorporating a standardized approach for add-on configuration within the OpAMP specification will enhance the flexibility, modularity, and overall manageability of the system.
The text was updated successfully, but these errors were encountered: