Skip to content

When importing legacy Data Query Templates, the Template can become unusable #5426

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

Closed
TheWitness opened this issue Jul 27, 2023 · 0 comments
Closed
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

In Cacti 1.2.23, we changed the index_type, index_value, and output_type to be always checked. Unfortunately, some older Cacti Data Templates did not have this enabled upon export. This causes those Data Query Data Templates to break post Cacti 1.2.23.

Expected behavior

Account for these Damaged Data Templates on import.

@TheWitness TheWitness added bug Undesired behaviour unverified Some days we don't have a clue labels Jul 27, 2023
@TheWitness TheWitness added this to the v1.2.25 milestone Jul 27, 2023
TheWitness added a commit that referenced this issue Jul 27, 2023
Importing a legacy Data Query Template can result in the Template being unusable
TheWitness added a commit that referenced this issue Jul 27, 2023
Importing a legacy Data Query Template can result in the Template being unusable
@TheWitness TheWitness added resolved A fixed issue confirmed Bug is confirm by dev team and removed unverified Some days we don't have a clue labels Jul 27, 2023
@netniV netniV changed the title Importing a legacy Data Query Template can result in the Template being unusable When importing legacy Data Query Templates, the Template can become unusable Sep 3, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Dec 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant