-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
When importing, make it possible to only import certain components #4820
Comments
- Make it possible to only import certain components when importing packages - This change is a pre-requisite for the upcoming Package plugin
Going to keep this open until I can fully test out the plugin. In theory this is enough. |
My only concern would be someone not realising what they are doing and wondering why a template breaks because of a partial import, but I can see the benefits too. |
Once I complete the package plugin, you will be able to see how this will work. You are right though, there might be some unintended consequences, but not for the trained eye. Anyway, more to follow. |
Taking off resolved until QA is complete |
Add support for package import from third part packages, also add the following import overrides when done through the GUI: * image_format * graph_width * graph_height
When importing, make it possible to only import certain components
Differences and orphans not rendering correctly.
Feature Request
Is your feature request related to a problem? Please describe
It is not possible to selectively import Cacti Template components
Describe the solution you'd like
Provide the ability for a plugin author to be able to selectively import certain components from a package. This might include Graph Templates, Data Queries, Data Sources, etc.
Describe alternatives you've considered
N/A
Additional context
Required for the public release of the Packaging Plugin
The text was updated successfully, but these errors were encountered: