On Fri, May 11, 2018 at 3:33 PM, nicolas de loof <[email protected]> wrote: > the exposed yaml model to > configure credentials should be defined as part of credential plugin, not by > me within configuration-as-code.
Well. JCasC likely needs some special handling for `Secret`, which `credentials` uses for the actual secrets inside. Beyond that, I agree that it makes sense for the specialized binding to ultimately live in `credentials-plugin`. But I take issue with two ways this was framed. First of all, there is nothing wrong with the design of credentials storage; it is sensible given the expected usage model. JCasC makes it easy to autobind configuration that lives all in one configuration screen. In this case, the UI is divided into different screens with a specialized UI, so specialized binding would be needed. Second, yes it needs to be defined “by you” (well, by whomever is striving to get JEP-201 accepted). Credentials are central to Jenkins setup and a critical use case for JEP-201. And JEP-201 is a new feature, so its developers are responsible for designing and implementing appropriate integrations with existing foundational components of Jenkins. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0eorvLJovVf9Fbut-zt0F9zDSvF_v0qa0ZsUrrz%2BoNAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
