We should make it clear in the docs about what is not supported. The expression parsing code was implementing in a way that never supported multiple expressions of the same type even with different resource contexts. This mean that neither of the following are supported: * multiple expressions of the same type using same resource context resource.trait[x] = foo resource.trait[y] = bar * multiple expressions of the same typing using different resource contexts resource.parent.trait[x] = foo resource.grandParent.trait[y] = bar
A slight extension of the limitation described in comment 1 is that a definition cannot also contain both resource configuration and plugin configuration expressions.
The CR1 build is available at https://brewweb.devel.redhat.com/buildinfo?buildID=231258. Moving to ON_QA.
Bulk closing of old issues in VERIFIED state.