But many things are otherwise preserved. I feel the implementation of the credentials configuration is doing a none vs. all approach, not taking into account existing entries:
In SystemCredentialsProviderConfigurator: target.setDomainCredentialsMap(DomainCredentials.asMap(value)) Maybe this code could be replaced to preserve existing entries. On Tuesday, September 25, 2018 at 10:03:00 PM UTC+2, damien.c...@collibra.com wrote: > > I've created the PR at > https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 to > show an unit test reproducing the issue. > > On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2, > damien.c...@collibra.com wrote: >> >> Hi, >> >> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is >> a list of credentials (some SSH keys, some user/passwords, etc.) common to >> all our instances but we let also the administrators of a Jenkins instance >> define their own credential entries. >> >> However, when the Jenkins instance is restarted, only the credential >> entries defined by the CasC files are kept, and all the ones which were >> added manually are lost. >> >> Is there a way to prevent this? >> >> Thanks, >> Damien Coraboeuf >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
