jenkinsci
/
configuration-as-code-plugin
mirror of https://github.com/jenkinsci/configuration-as-code-plugin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add Azure KeyVault to secrets doc (#1321)

This commit is contained in:
Tim Jacomb 2020-03-14 09:52:00 +00:00 committed by GitHub
parent 4b9cc7e2ab
commit 7f6bab4ebb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/features/secrets.adoc
View File

@ -20,6 +20,7 @@ Examples of available plugins:
* link:https://plugins.jenkins.io/kubernetes-credentials-provider[Kubernetes Credentials Provider]
* link:https://plugins.jenkins.io/aws-secrets-manager-credentials-provider[AWS Secrets Manager Credentials Provider]
* link:https://plugins.jenkins.io/azure-keyvault[Azure KeyVault]
* link:https://go.cloudbees.com/docs/cloudbees-core/cloud-secure-guide/cyberark/#cyberark-credentials-provider[CyberARK Credential Provider] (proprietary plugin offered by CloudBees)
When an external Credentials provider is configured in Jenkins through JCasC, there is no need to define credentials inside.
@ -78,6 +79,7 @@ We can provide these initial secrets in the following ways:
- Using Docker Secrets
- Using Kubernetes secrets
- Using HashiCorp Vault
- link:https://github.com/jenkinsci/azure-keyvault-plugin#secretsource[Using Azure KeyVault]
- Using environment variables
==== Docker secrets