-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Copy integration policy #75868
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
Even better would be the ability to just include an existing integration policy onto a new agent policy. Copying the integration policy would solve different use cases, but in many cases I'd prefer that if I need an integration on a particular server it functions the same way that I've configured that integration on all other servers where it's in use. |
Ah, good to know! |
Has there been any headway made on this proposal? |
If a user wants to create a new integrations policy, currently the user has to always start from scratch. But often it might be useful to copy an existing policy with all the params and adjust it. To make this possible the proposal here is that either when looking at the policy list of an Agent Config or when adding an Integration to an Agent Policy, the user can select existing policies.
If the user selects an existing policy and clicks copy, the integration editing screen shows up with the prefilled values. The new integration policy has its own id.
If a policy is copied, no copy exist before the user hit Save from the edit screen. This is important as the copy only takes effect after modifying all configuration options. In case the copy option is from the policy list of an Agent Config, the user could select the target Agent Policy to copy it to. At first, we could support only 1 workflow.
The text was updated successfully, but these errors were encountered: