Closed timja closed 5 years ago
If anyone has any ideas on this help appreciated, have debugged through it a bit :(
Doesn't make sense to validate a full export()
take the approach done in plugin module and in metrics plugn: https://github.com/jenkinsci/metrics-plugin/pull/43
Tried that here: https://github.com/jenkinsci/azure-keyvault-plugin/pull/15
Didn't work 😢 I wonder if it's anything to do with it being a global configuration class and its not being picked up.
It's weird though because it does actually work, I just can't get a test that contains the config
This unit test fails: https://github.com/jenkinsci/azure-keyvault-plugin/blob/51dd43f5c1ee915de6da9c4c4b0a0c9e5f5b4b67/src/test/java/org/jenkinsci/plugins/azurekeyvaultplugin/ConfigAsCodeTest.java#L40
But works when exported manually from the UI The databinding unit test passes for importing the configuration as code yaml
The exported yaml file from the unit test export is:
It's missing the azureKeyVault section:
Example exported from UI:
Anyone got any ideas? Something I'm doing that's wrong? Or is this a bug, it's weird that if I export from the UI it works though
Startup log: