User story #1561

history and DEV/QA/Prod statuses on changes for a policy

Added by Fabrice FLORE-THÉBAULT over 6 years ago. Updated over 5 years ago.

Web - Config management
Target version (plugin):
Suggestion strength:
User visibility:
Effort required:
Pull Request:


When executing some changes on an already existing policy, we should be able to keep an history of the changes, and have a validation workflow.

Let's say we change one setting on the ssh server configuration.
First, we will change the setting on the policy, and the saved policy will get the status "DEV".
For nodes flagged as production nodes, the applied policy will still be the old "Production" policy until the "DEV" status is changed for "Production" status.
For nodes flagged as development nodes, the DEV, rep. QA, resp Prod policy will be applied.
For nodes flagged as QA nodes, the QA, resp Prod policy will be applied.

In the same time, this will permit to keep an history of policies, nice to have would be to have a retention policy (keep policies for 1 year for dev, 2 years for prod).


#1 Updated by François ARMAND over 6 years ago

  • Target version changed from 10 to 24

#2 Updated by Jonathan CLARKE over 5 years ago

  • Target version changed from 24 to Ideas (not version specific)

Also available in: Atom PDF