@Will Cho Yes, it does. It might not be a solution for this particular "already deployed" situation, but you might want to consider it for future situations.
Just a quick question. Why do they open up the existing ruleset version and make the changes? Why not create a new ruleset version on top of the "buggy" version, duplicate the rules and disable it in that version?
Posted: 1 year ago
Posted: 14 Apr 2022 7:39 EDT
Will Cho (Will Cho)
Principal System Architect
@Michel Kraaij i don't know. I was just brought into as a new tech lead on DevOps and this was how they were doing before. I explained that unlocking rulesets in DEV to changes rules that were previously deployed to QA is risky and not best practice. So here i'm trying to find a new solution before deprecating the old practice.
I also suggested to open up a new version and withdraw the rules. One caveat is that this should work for new rules, but for existing rules it can also withdraw all rules in the same ruleset and can break the application.
If you see any alternative solution, that would be appreciated.