Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit73bfb82

Browse files
added page for hashicorp-vault (#249)
* added page for hashicorp-vault* made edits* fixed broken link* removed space
1 parent5015a98 commit73bfb82

File tree

4 files changed

+59
-1
lines changed

4 files changed

+59
-1
lines changed

‎_data/nav.yml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -413,7 +413,9 @@
413413
-title:"Other Registries"
414414
url:"/other-registries"
415415
-title:Secret Storage
416-
url:"/secret-storage"
416+
url:"/secret-storage"
417+
-title:Hashicorp Vault
418+
url:"/hashicorp-vault"
417419
-title:Helm Integration
418420
url:"/helm"
419421
-title:ArgoCD Integration
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title:"Hashicorp Vault"
3+
description:"How to use secrets from Vault in your Codefresh pipelines"
4+
group:integrations
5+
toc:true
6+
---
7+
8+
Codefresh can use secrets from your Hashicorp Vault installation. This way you have full control over secret storage and rotation.
9+
10+
>Note: This feature is for Enterprise accounts only.
11+
12+
###Prerequisites
13+
14+
You need to have a vault instance up and running. Codefresh supports Vault instances that run on the cloud, as well as behind the firewall (albeit with some differences in the authentication methods).
15+
16+
You also need to decide what[authentication method](https://www.vaultproject.io/docs/auth) Codefresh will use. The following methods are supported:
17+
18+
---|---
19+
[Username/Password](https://www.vaultproject.io/docs/auth/userpass)|Available in SaaS and Hybrid customers
20+
[Access Token](https://www.vaultproject.io/docs/auth/token)|Available in SaaS and Hybrid customers
21+
[Kubernetes](https://www.vaultproject.io/docs/auth/kubernetes)|Only available in[Hybrid installation]({{site.baseurl}}/docs/docs/administration/behind-the-firewall/)
22+
[Google Cloud Engine](https://www.vaultproject.io/docs/auth/gcp)|Only available in[Hybrid installation]({{site.baseurl}}/docs/docs/administration/behind-the-firewall/)
23+
[App Role]()|Available in SaaS and Hybrid customers
24+
25+
###Using the Codefresh UI
26+
27+
On the left-hand panel, navigate to**Account Settings** >**Integrations** >**Secret Store** and select**Configure**.
28+
29+
Click on**Add Provider** and select**Hashicorp vault**. Toggle the “allow access to all users” button to the off position as you normally want only Codefresh admins to change vault configuration.
30+
31+
{% include image.html
32+
lightbox="true"
33+
file="/images/integrations/hashicorp-vault/hashicorp-vault.png"
34+
url="/images/integrations/hashicorp-vault/hashicorp-vault.png"
35+
alt="Hashicorp-vault Secret"
36+
caption="Hashicorp-vault Secret"
37+
max-width="80%"
38+
%}
39+
40+
Enter a name for your integration (you can have multiple vault integrations) unique to this configuration. Then choose if your vault instance is behind a firewall or not.
41+
42+
The rest of the options are specific to your[Vault authentication](https://www.vaultproject.io/docs/auth) method and you should consult the Vault documentation on how to obtain them.
43+
44+
###Using the Codefresh CLI
45+
46+
You can also create Vault integrations with the[CLI](https://codefresh-io.github.io/cli/) and more specifically with the[create context command](https://codefresh-io.github.io/cli/contexts/create-context/create-secret-store-context/hashicorp-vault/).
47+
48+
The available options are the same ones as found in the UI. For example, to create an integration with user/pass authentication the respective command is:
49+
50+
`codefresh create context secret-store hashicorp-vault my-integration --sharing-policy AccountAdmins -app-url http://vault.example.com --username my-user --password my-password`
51+
52+
53+
###Using the Secrets
54+
55+
To use the vault secrets in pipelines see our[secrets guide]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/secrets-store/). Note that because in Vault, a secret can contain multiple key-value pairs you will need to put in the key name as well. So the syntax will be`{secrets.vault-store-name.path/to/secret@key}`

‎_docs/whats-new/whats-new.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ toc: true
1515

1616
###March 2021
1717

18+
- Native Support for Hashicorp Vault Secrets -[documentation]({{site.baseurl}}/docs/integrations/hashicorp-vault)
1819
- Blue/Green deployments with Argo Rollouts -[documentation]({{site.baseurl}}/docs/ci-cd-guides/progressive-delivery/#blue-green-deployments)
1920
- The[Modified Files filter]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/#monorepo-support-modified-files) will now work on triggers triggered by Pull Request events. Notice: this might cause unexpected behavior if you have a trigger that is triggered by both Pull Request and Commit events with a Modified Files filter set. Previously the Modified Files filter would be ignored for Pull Request events. If you need different filters for Pull Requests and Commit events, we recommend you separate the trigger.
2021
- Codefresh Runner on Rancher RKE 2.X -[documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#installing-on-rancher-rke-2x)
44.9 KB
Loading

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp