Page 1 of 1

[SOLVED] tis-add-dev-maturity issue

Published: March 20, 2026 - 4:20 PM
by tux
Hello,

I have a question about how maturity works.
Once the "tis-add-dev-maturity" package is installed, the maturity defined by the package is overwritten.

Is there a conflict between the JSON files generated by the dynamic configuration packages and the way the "tis-add-dev-maturity" package works?

Re: Question tis-add-dev-maturity

Published: March 23, 2026 - 10:33
by fschelfaut
Hello Sébastien,

The tis-add-dev-maturity package should no longer be used if dynamic configuration packages are already deployed on your network.
From now on, agent settings must be managed via these dynamic configuration packages.

If you wish to replicate the behavior of this package, I recommend creating a dynamic configuration package instead and defining the following maturity level: PROD, PREPROD.

We will remove the tis-add-dev-maturity package from the store as it is no longer needed.

Flavien,

[SOLVED] Re: tis-add-dev-maturity question

Published: March 23, 2026 - 3:02 PM
by tux
Hello,

thank you for your feedback.