Mar 23, 2021 · Mar 21, 2021 · Mar 22, 2021 · Mar 22, 2021 · Mar 23, 2021 · Mar 22, 2021
diff --git a/_data/nav.yml b/_data/nav.yml
        - title: "Other Registries"
          url: "/other-registries"
    - title: Secret Storage
      url: "/secret-storage"
      url: "/secret-storage"
    - title: Hashicorp Vault
      url: "/hashicorp-vault"
    - title: Helm Integration
      url: "/helm"
    - title: ArgoCD Integration
diff --git a/_docs/integrations/hashicorp-vault.md b/_docs/integrations/hashicorp-vault.md
 ---
 title: "Hashicorp Vault"
 description: "How to use secrets from Vault in your Codefresh pipelines"
 group: integrations
 toc: true
 ---

 Codefresh can use secrets from your Hashicorp Vault installation. This way you have full control over secret storage and rotation.

 >Note: This feature is for Enterprise accounts only.

 ### Prerequisites

 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).

 You also need to decide what [authentication method](https://www.vaultproject.io/docs/auth) Codefresh will use. The following methods are supported:

 ---|---
 [Username/Password](https://www.vaultproject.io/docs/auth/userpass)|Available in SaaS and Hybrid customers
 [Access Token](https://www.vaultproject.io/docs/auth/token)|Available in SaaS and Hybrid customers
 [Kubernetes](https://www.vaultproject.io/docs/auth/kubernetes)|Only available in [Hybrid installation]({{site.baseurl}}/docs/docs/administration/behind-the-firewall/)
 [Google Cloud Engine](https://www.vaultproject.io/docs/auth/gcp)|Only available in [Hybrid installation]({{site.baseurl}}/docs/docs/administration/behind-the-firewall/)
 [App Role]()|Available in SaaS and Hybrid customers

 ### Using the Codefresh UI

 On the left-hand panel, navigate to **Account Settings** > **Integrations** > **Secret Store** and select **Configure**.

 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.

 {% include image.html
 lightbox="true"
 file="/images/integrations/hashicorp-vault/hashicorp-vault.png"
 url="/images/integrations/hashicorp-vault/hashicorp-vault.png"
 alt="Hashicorp-vault Secret"
 caption="Hashicorp-vault Secret"
 max-width="80%"
  %}

 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.

 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.

 ### Using the Codefresh CLI

 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/).

 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:

 `codefresh create context secret-store hashicorp-vault my-integration --sharing-policy AccountAdmins -app-url http://vault.example.com --username my-user --password my-password`


 ### Using the Secrets

 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}`
diff --git a/_docs/whats-new/whats-new.md b/_docs/whats-new/whats-new.md

 ### March 2021

 - Native Support for Hashicorp Vault Secrets - [documentation]({{site.baseurl}}/docs/integrations/hashicorp-vault)
 - Blue/Green deployments with Argo Rollouts - [documentation]({{site.baseurl}}/docs/ci-cd-guides/progressive-delivery/#blue-green-deployments)
 - 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.
 - Codefresh Runner on Rancher RKE 2.X - [documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#installing-on-rancher-rke-2x)
diff --git a/images/integrations/hashicorp-vault/hashicorp-vault.png b/images/integrations/hashicorp-vault/hashicorp-vault.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -413,7 +413,9 @@
		- title: "Other Registries"
		url: "/other-registries"
		- title: Secret Storage
		url: "/secret-storage"
		url: "/secret-storage"
		- title: Hashicorp Vault
		url: "/hashicorp-vault"
		- title: Helm Integration
		url: "/helm"
		- title: ArgoCD Integration
Expand Down
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,55 @@
		---
		title: "Hashicorp Vault"
		description: "How to use secrets from Vault in your Codefresh pipelines"
Copy link Member kostis-codefreshMar 22, 2021 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. This is a new feature. We need an entry in the what's new page.
		group: integrations
		toc: true
		---

		Codefresh can use secrets from your Hashicorp Vault installation. This way you have full control over secret storage and rotation.

		>Note: This feature is for Enterprise accounts only.

		### Prerequisites

		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).

		You also need to decide what [authentication method](https://www.vaultproject.io/docs/auth) Codefresh will use. The following methods are supported:

		---\|---
		[Username/Password](https://www.vaultproject.io/docs/auth/userpass)\|Available in SaaS and Hybrid customers
		[Access Token](https://www.vaultproject.io/docs/auth/token)\|Available in SaaS and Hybrid customers
		[Kubernetes](https://www.vaultproject.io/docs/auth/kubernetes)\|Only available in [Hybrid installation]({{site.baseurl}}/docs/docs/administration/behind-the-firewall/)
		[Google Cloud Engine](https://www.vaultproject.io/docs/auth/gcp)\|Only available in [Hybrid installation]({{site.baseurl}}/docs/docs/administration/behind-the-firewall/)
		[App Role]()\|Available in SaaS and Hybrid customers

		### Using the Codefresh UI

		On the left-hand panel, navigate to Account Settings > Integrations > Secret Store and select Configure.

		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.

		{% include image.html
		lightbox="true"
		file="/images/integrations/hashicorp-vault/hashicorp-vault.png"
		url="/images/integrations/hashicorp-vault/hashicorp-vault.png"
		alt="Hashicorp-vault Secret"
		caption="Hashicorp-vault Secret"
		max-width="80%"
		%}

		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.

		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.

		### Using the Codefresh CLI

		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/).

		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:

		`codefresh create context secret-store hashicorp-vault my-integration --sharing-policy AccountAdmins -app-url http://vault.example.com --username my-user --password my-password`


		### Using the Secrets

		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}`
Original file line number	Diff line number	Diff line change
Expand Up		@@ -15,6 +15,7 @@ toc: true

		### March 2021

		- Native Support for Hashicorp Vault Secrets - [documentation]({{site.baseurl}}/docs/integrations/hashicorp-vault)
		- Blue/Green deployments with Argo Rollouts - [documentation]({{site.baseurl}}/docs/ci-cd-guides/progressive-delivery/#blue-green-deployments)
		- 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.
		- Codefresh Runner on Rancher RKE 2.X - [documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#installing-on-rancher-rke-2x)
Expand Down