Add support for configuring envinject-plugin global configs with the configuration-as-code plugin
What needs to be done to move this forward? How can I help?
From what I can see the PR looks to surface the config values that appear on the `configureSecurity/` page, which is a good start.
I was hoping to have the JCASC yaml be able to set all the "Global Passwords" entries which appear on the `configure/` page. Is that a similar effort as this, by exposing some strategic attributes, or is it a lot more complicated?
The fix was released in EnvInject 2.2.0