Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
None
-
None
-
None
Description
If you declare a Property of a processor with a list of allowed values (using withAllowableValues) and then give this property a non-allowed value when you configure the processor, it will not automatically throw an exception, only if the processor code checks the property in onSchedule().
The heartbeat will contain the list of allowed values, so if you use a C2 client to set up the configuration, then this can be prevented by the client, so this is not a major issue.
Nevertheless, the Property itself should verify that it is valid, so each processor doesn't need to check them in onSchedule(), or risk not working correctly when configured manually. Since this change may break existing deployments, it should be rolled out with a major version change.
Attachments
Issue Links
- is duplicated by
-
MINIFICPP-1238 Implement features to prevent working with incomplete flow
- Open
-
MINIFICPP-1269 Global flow configuration verification
- Open