Thanks Jesse, the solution was indeed to implement a custom
RootElementConfigurator in the plugin. (And then to do the translation between
the desired CasC config model and the traditional Web form config model in the
describe() method.)
Chris
> On 11 Feb 2020, at 16:54, Jesse Glick wrote:
The `structs` API defines a `CustomDescribableModel` for this sort of
thing, used for example by Pipeline. However `configuration-as-code`
has its own incompatible model. I think you can implement either
`RootElementConfigurator` or `Configurable`.
--
You received this message because you are
Hello,
I'm adding an optional list property to a plugin's configuration. This is a
particularly tricky kind of property, as it results in lots of nesting in the
config data model to make the Web UI's /configure page work. I would like to
present a simpler data model to CasC without the
