C
Consistent Crab
We are experimenting "warn and continue" with policy as code for Harness FME.
Two issues:
  1. For a feature flag change, when there is no approval needed, the warning only appears after the change is made. It's better to warn before the change is made. "warn and continue" is the better than "continue and warn".
  2. Same for a feature flag change, when there is approval needed, the warning only appears after the change is approved and made on the approver side. This basically makes the feature useless because the whole point of an approval is to review the change, worse, it's actually the approver let the change in under this scenario.
I understand the feature clearly indicate the rules are evaluated "on save", so it's legit engineering flow. The feature will provide much more value if the warning are displayed before the actual change is made, IMHO, an extra step to let people confirm before proceed.
Thanks.