Branch: refs/heads/master
  Home:   https://github.com/jenkinsci/config-file-provider-plugin
  Commit: 3f330ad7f8dc22c7c3e3a4f7a915845c88b6ea0b
      
https://github.com/jenkinsci/config-file-provider-plugin/commit/3f330ad7f8dc22c7c3e3a4f7a915845c88b6ea0b
  Author: Andrew Grimberg <[email protected]>
  Date:   2021-03-15 (Mon, 15 Mar 2021)

  Changed paths:
    M pom.xml
    M src/main/java/org/jenkinsci/lib/configprovider/model/ContentType.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/AbstractCustomProvider.java
    M src/main/java/org/jenkinsci/plugins/configfiles/custom/CustomConfig.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/CustomConfigCredentialsHelper.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/HasCustomizedCredentialMappings.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/TokenKeyRequirement.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/TokenValueMacro.java
    M 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/CustomConfig/edit-config.jelly
    M 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/CustomConfig/show-config.jelly
    A 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping/config.jelly
    A 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping/help-credentialsId.html
    A 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping/help-tokenKey.html

  Log Message:
  -----------
  Add credential management to custom files

With the advent of Jenkins Configuration As Code (JCasC) it has become
more needed to be able to provide a way to allow job owners to provide
new managed configuration files that also replace tokenized credentials.
While it is possible to attain this goal by utilizing the Credentials
Binding Plugin along with the 'Replace All' option when defining where
the file is put on disk during the job this has caused several problems
with well established methods of managing the jobs. In particular, jobs
being managed with Jenkins Job Builder which tend to be heavily
Freestyle in nature and also utilize a lot of templates and macros
suffer greatly when using this method of management.

Instead, allowing credentials to be defined and automatically replaced
when the file is rendered down to disk solves the problem of securely
storing the credentials in the credential store and also allowing less
privileged persons the ability to more easily work with the managed
files.

This change in particular modifies the 'custom' file type to support
defining credentials along with the tokens that are to be used and
having them properly rendered when being put down on disk. It will
continue to work fine with the previous method using the Credentials
Binding Plugin as well as it will only replace the tokens that it has a
full definition for and then would be passed through the full
environment token replacement as well as it did before this change.

Making this change allows for safe storage of configuration files in
JCasC format to be stored in a repository and in some fashion
manipulated into place for Jenkins to utilize (exercise for the admin)
which is a partial answer to JENKINS-17766. It also completely obviates
the requirement to encrypt the files as per JENKINS-18635 as the
sensitive data can now be securely separated from the non-sensitive
data.

Resolves: JENKINS-43204
Signed-off-by: Andrew Grimberg <[email protected]>


  Commit: b09f3d46ef61812aecc2dc5e36c3cf944a88e30a
      
https://github.com/jenkinsci/config-file-provider-plugin/commit/b09f3d46ef61812aecc2dc5e36c3cf944a88e30a
  Author: Ramon Leon <[email protected]>
  Date:   2021-04-21 (Wed, 21 Apr 2021)

  Changed paths:
    M pom.xml
    M src/main/java/org/jenkinsci/lib/configprovider/model/ContentType.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/AbstractCustomProvider.java
    M src/main/java/org/jenkinsci/plugins/configfiles/custom/CustomConfig.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/CustomConfigCredentialsHelper.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/HasCustomizedCredentialMappings.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/TokenKeyRequirement.java
    A 
src/main/java/org/jenkinsci/plugins/configfiles/custom/security/TokenValueMacro.java
    M 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/CustomConfig/edit-config.jelly
    M 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/CustomConfig/show-config.jelly
    A 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping/config.jelly
    A 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping/help-credentialsId.html
    A 
src/main/resources/org/jenkinsci/plugins/configfiles/custom/security/CustomizedCredentialMapping/help-tokenKey.html

  Log Message:
  -----------
  Merge pull request #90 from tykeal/tokenized


Compare: 
https://github.com/jenkinsci/config-file-provider-plugin/compare/d615e3278358...b09f3d46ef61

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" 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-commits/jenkinsci/config-file-provider-plugin/push/refs/heads/master/d615e3-b09f3d%40github.com.

Reply via email to