Bug #9166
closedEnabling Allows ${node.properties[key]} expansion in Directives for key->value and key->json doesn't trigger a regeneration
Description
When enabling "Allows ${node.properties[key]} expansion in Directives for key->value and key->json" on settings page, it did not triggered a regeneration, so my policies with node.properties didn't expand correctly
Updated by François ARMAND over 7 years ago
It is the intended behaviour: we wanted to let the user review existing node properties, which he should not have in directive parameter, before generating. Because else, you don't have a chance to add ${node.properties[...] | node} in them.
So, to sum up:
- user should not have ${node.properties} in directive parameters (so no generation needed),
- if they have, it's because they used to have them expanded in the node, so maybe they want to add ${... | node } on them (so no generation before that).
Do you think it should be otherwise?
Updated by François ARMAND almost 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Infrequent - complex configurations | third party integrations
- Effort required set to Small
- Priority changed from 0 to 13
So, the change must trigger a generation. If the generation fails, the user can still disable it again.
Updated by Jonathan CLARKE almost 7 years ago
- Assignee deleted (
François ARMAND)
Updated by François ARMAND over 5 years ago
- Status changed from New to Rejected
The option is always enabled now.