As of Cumulus 16.1.1, onetime rules that have their state set to DISABLED are no longer capable of triggering workflow execution. This was a bug that was fixed. Further, even rules with their state set to ENABLED are no longer automatically executed when they are first added to the Cumulus DB.
This means that we can now remove our workaround to prevent unwanted rule execution.
Acceptance criteria:
[x] app/stacks/cumulus/templates/discover-granules-workflow.asl.json is updated such that it:
[x] no longer has a RuleEnabled? step
[x] no longer has a SkipWorkflow step
[x] has its start state set to SelfDiscovery?
[x] All rule definitions have the meta.rule block removed
[x] The rule template file _templates/rule/new/rule.ejs.t has its meta.rule block removed
[x] The Appendix (describing our now-obsolete workaround) is removed from docs/OPERATING.md
As of Cumulus 16.1.1, onetime rules that have their
stateset toDISABLEDare no longer capable of triggering workflow execution. This was a bug that was fixed. Further, even rules with theirstateset toENABLEDare no longer automatically executed when they are first added to the Cumulus DB.This means that we can now remove our workaround to prevent unwanted rule execution.
Acceptance criteria:
app/stacks/cumulus/templates/discover-granules-workflow.asl.jsonis updated such that it:RuleEnabled?stepSkipWorkflowstepSelfDiscovery?meta.ruleblock removed_templates/rule/new/rule.ejs.thas itsmeta.ruleblock removeddocs/OPERATING.md