Skip to content

Commit f9e13e7

Browse files
RubenSandwichbrianshumateyhyakunaLeahMarieBushwilliamdalessandro
authored
Repo sync (#557)
* Add doc to concepts and nav for all versions * Update content/vault/v1.20.x/content/docs/concepts/secure-cluster-with-tls.mdx Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com> * move to Deploy * move to Deploy nav * add hcp-docs to develop * adding in semi latest changes to hcp-docs * add labeling * adding in prebuild binaries * Add PR template, and HCP doc specific template * Suggested changes * Updated steps for PR config * compress images * chore: add hcp-docs codeowners * refactoring.mdx type "mulitple" * typo: collision * Convert image to reusable partial * Revert "add labeling" This reverts commit 91cb4a0. * Revert "adding in prebuild binaries" This reverts commit da2a28e. * add labeling * Adding in latest changes from repo * updated prebuild binaries * add ldap events * update important changes docs * fix sample request and response * Added centralize packages doc. * suggested edits (#1121) * Fix links (#1135) * fix: update the partials directory for non-versioned docs (#1136) * fix: update the partials directory for non-versioned docs * fix tests --------- Co-authored-by: Brian Shumate <brian@hashicorp.com> Co-authored-by: Brian Shumate <brianshumate@users.noreply.github.com> Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com> Co-authored-by: Leah Bush <leah.bush@hashicorp.com> Co-authored-by: William Dalessandro <will.dalessandro@hashicorp.com> Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com> Co-authored-by: Ruben Nic <ruben.nic@hashicorp.com> Co-authored-by: Robin Neatherway <robin.neatherway@gmail.com> Co-authored-by: Rémy Léone <rleone@scaleway.com> Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com> Co-authored-by: Baraa Basata <bbasata@gmail.com> Co-authored-by: cbiguet <constantin.biguet@gmail.com> Co-authored-by: Jaired Jawed <jaired.jawed@hashicorp.com> Co-authored-by: rculpepper <rculpepper@hashicorp.com> Co-authored-by: Anthony <russo555@gmail.com> Co-authored-by: Craig Wright <crw@crw.xyz> Co-authored-by: williamdalessandro <william.dalessandro@ibm.com> Co-authored-by: Rachel Culpepper <84159930+rculpepper@users.noreply.github.com> Co-authored-by: Constantin Biguet <55029503+cbiguet@users.noreply.github.com> Co-authored-by: Rose M Koron <32436232+rkoron007@users.noreply.github.com> Co-authored-by: Leah Bush <157434496+LeahMarieBush@users.noreply.github.com>
2 parents 2729e6b + 3c0d677 commit f9e13e7

File tree

22 files changed

+248
-17
lines changed

22 files changed

+248
-17
lines changed

‎CODEOWNERS‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,3 +38,19 @@
3838
# Well-architected framework
3939

4040
/content/well-architected-framework/ @hashicorp/well-architected-education-approvers
41+
42+
43+
# HCP-docs documentation ownership
44+
# HCP Consul Docs
45+
/content/hcp-docs/content/docs/consul/* @hashicorp/consul-docs
46+
47+
# HCP Vault & HCP Vault Secrets docs
48+
/content/hcp-docs/content/docs/vault/* @hashicorp/vault-education-approvers
49+
/content/hcp-docs/content/docs/vault-secrets/* @hashicorp/vault-education-approvers
50+
51+
# HCP Boundary docs
52+
/content/hcp-docs/content/docs/boundary/* @hashicorp/boundary-education-approvers
53+
54+
#HCP IAM
55+
/content/hcp-docs/content/partials/hcp-administration/* @hashicorp/cloud-access-control @hashicorp/cloud-identity
56+
/content/hcp-docs/content/docs/hcp/iam/* @hashicorp/cloud-access-control @hashicorp/cloud-identity

‎content/terraform/v1.13.x/docs/language/stacks/deploy/conditions.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ deployment_auto_approve "no_changes" {
5252

5353
</CodeBlockConfig>
5454

55-
The `condition` argument in the `deployment_auto_approve` block has access to the `context` of the current deployment run. To learn more about `context`, refer to the [`deployment_auto_approve` reference](/terraform/language/block/stack/deploy/deployment_auto_approve#deployment-plan-context).
55+
The `condition` argument in the `deployment_auto_approve` block has access to the `context` of the current deployment run. To learn more about `context`, refer to the [`deployment_auto_approve` reference](/terraform/language/block/stack/tfdeploy/deployment_auto_approve#deployment-plan-context).
5656

5757
After defining your auto-approval rule, add that rule to your deployment group using the `auto_approve_checks` argument. In the following example, the `staging_group` deployment group enforces the `no_changes` rule:
5858

‎content/terraform/v1.13.x/docs/language/stacks/deploy/config.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ deployment "web" {
216216

217217
Now, whenever the `web` deployment generates a deployment run that does not destroy resources, HCP Terraform automatically approves that run.
218218

219-
If you don't assign a deployment to a group, Terraform automatically creates a default deployment group for that deployment. To learn more about defining deployment groups, refer to the [`deployment_group` reference](/terraform/language/block/stack/deploy/deployment_group). To learn more about setting up deployment group orchestration rules, refer to [Set conditions for deployment runs](/terraform/language/stacks/deploy/conditions).
219+
If you don't assign a deployment to a group, Terraform automatically creates a default deployment group for that deployment. To learn more about defining deployment groups, refer to the [`deployment_group` reference](/terraform/language/block/stack/tfdeploy/deployment_group). To learn more about setting up deployment group orchestration rules, refer to [Set conditions for deployment runs](/terraform/language/stacks/deploy/conditions).
220220

221221
## Next steps
222222

‎content/terraform/v1.14.x (beta)/docs/language/stacks/deploy/conditions.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ deployment_auto_approve "no_changes" {
5252

5353
</CodeBlockConfig>
5454

55-
The `condition` argument in the `deployment_auto_approve` block has access to the `context` of the current deployment run. To learn more about `context`, refer to the [`deployment_auto_approve` reference](/terraform/language/block/stack/deploy/deployment_auto_approve#deployment-plan-context).
55+
The `condition` argument in the `deployment_auto_approve` block has access to the `context` of the current deployment run. To learn more about `context`, refer to the [`deployment_auto_approve` reference](/terraform/language/block/stack/tfdeploy/deployment_auto_approve#deployment-plan-context).
5656

5757
After defining your auto-approval rule, add that rule to your deployment group using the `auto_approve_checks` argument. In the following example, the `staging_group` deployment group enforces the `no_changes` rule:
5858

‎content/terraform/v1.14.x (beta)/docs/language/stacks/deploy/config.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ deployment "web" {
216216

217217
Now, whenever the `web` deployment generates a deployment run that does not destroy resources, HCP Terraform automatically approves that run.
218218

219-
If you don't assign a deployment to a group, Terraform automatically creates a default deployment group for that deployment. To learn more about defining deployment groups, refer to the [`deployment_group` reference](/terraform/language/block/stack/deploy/deployment_group). To learn more about setting up deployment group orchestration rules, refer to [Set conditions for deployment runs](/terraform/language/stacks/deploy/conditions).
219+
If you don't assign a deployment to a group, Terraform automatically creates a default deployment group for that deployment. To learn more about defining deployment groups, refer to the [`deployment_group` reference](/terraform/language/block/stack/tfdeploy/deployment_group). To learn more about setting up deployment group orchestration rules, refer to [Set conditions for deployment runs](/terraform/language/stacks/deploy/conditions).
220220

221221
## Next steps
222222

‎content/vault/v1.19.x/content/docs/deploy/why-use-tls.mdx‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
layout: docs
3+
page_title: Why use TLS?
4+
description: >-
5+
Understand the benefits of securing your Vault clusters with end-to-end TLS.
6+
---
7+
8+
# Why use TLS?
9+
10+
You can enhance the overall security posture of your Vault cluster when you
11+
secure communications with TLS to ensure that data transmitted between Vault
12+
nodes and clients remains confidential and tamper-proof.
13+
14+
@include 'ld-images/deploy/secure-vault-tls.mdx'
15+
16+
Use mutual TLS with your Vault cluster deployments to protect sensitive data and
17+
prevent unauthorized access with enhanced compliance, governance, auditing
18+
capabilities, and incident response.
19+
20+
## TLS benefits
21+
22+
- **Improved data protection**.
23+
TLS prevents unauthorized access or communication with the Vault cluster to
24+
ensure data availability based on your security policies. TLS also protects
25+
sensitive data in transit to prevent interception or tampering.
26+
27+
- **Strong identity verification**.
28+
Vault cluster nodes and clients verify identities from TLS certificates before
29+
communicating to enable trusted operations and prevent impersonation.
30+
31+
- **Improved compliance and governance**.
32+
Implementing mutual TLS in your Vault clusters aligns your deployments with
33+
industry best practices and regulatory requirements like HIPAA, PCI-DSS, and
34+
others.
35+
36+
- **Reduce risk of data leaks**.
37+
When you operate Vault clusters with mutual TLS enabled, you minimize the risk
38+
of data leaks and unauthorized access to sensitive information.
39+
40+
- **Improved incident response**.
41+
Mutual TLS helps to limit the exposure or damage from unauthorized access to
42+
sensitive data stored in Vault, which makes incident response more
43+
straightforward.
44+
45+
## TLS resources
46+
47+
- [Default Vault TLS configuration](/vault/docs/configuration/listener/tcp#default-tls-configuration)
48+
- [Configure TLS for your Vault TCP listener](/vault/docs/configuration/listener/tcp/tcp-tls)
49+
- [Vault installation to minikube via Helm with TLS enabled](/vault/tutorials/kubernetes/kubernetes-minikube-tls)
50+
- [Medium blog: Enabling TLS on your Vault cluster on Kubernetes](https://medium.com/@martin.hodges/enabling-tls-on-your-vault-cluster-on-kubernetes-0d20439b13d0)

‎content/vault/v1.19.x/content/partials/ld-images/deploy/secure-vault-tls.mdx‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
<ImageConfig hideBorder>
2+
3+
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls-dark.png#dark-theme-only)
4+
5+
</ImageConfig>
6+
7+
<ImageConfig hideBorder>
8+
9+
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls.png#light-theme-only)
10+
11+
</ImageConfig>

‎content/vault/v1.19.x/data/docs-nav-data.json‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -666,6 +666,10 @@
666666
{
667667
"title": "Deploy Vault",
668668
"routes": [
669+
{
670+
"title": "Why use TLS?",
671+
"path": "deploy/why-use-tls"
672+
},
669673
{
670674
"title": "Run as a service",
671675
"path": "deploy/run-as-service"

‎content/vault/v1.20.x/content/docs/deploy/why-use-tls.mdx‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
layout: docs
3+
page_title: Why use TLS?
4+
description: >-
5+
Understand the benefits of securing your Vault clusters with end-to-end TLS.
6+
---
7+
8+
# Why use TLS?
9+
10+
You can enhance the overall security posture of your Vault cluster when you
11+
secure communications with TLS to ensure that data transmitted between Vault
12+
nodes and clients remains confidential and tamper-proof.
13+
14+
@include 'ld-images/deploy/secure-vault-tls.mdx'
15+
16+
Use mutual TLS with your Vault cluster deployments to protect sensitive data and
17+
prevent unauthorized access with enhanced compliance, governance, auditing
18+
capabilities, and incident response.
19+
20+
## TLS benefits
21+
22+
- **Improved data protection**.
23+
TLS prevents unauthorized access or communication with the Vault cluster to
24+
ensure data availability based on your security policies. TLS also protects
25+
sensitive data in transit to prevent interception or tampering.
26+
27+
- **Strong identity verification**.
28+
Vault cluster nodes and clients verify identities from TLS certificates before
29+
communicating to enable trusted operations and prevent impersonation.
30+
31+
- **Improved compliance and governance**.
32+
Implementing mutual TLS in your Vault clusters aligns your deployments with
33+
industry best practices and regulatory requirements like HIPAA, PCI-DSS, and
34+
others.
35+
36+
- **Reduce risk of data leaks**.
37+
When you operate Vault clusters with mutual TLS enabled, you minimize the risk
38+
of data leaks and unauthorized access to sensitive information.
39+
40+
- **Improved incident response**.
41+
Mutual TLS helps to limit the exposure or damage from unauthorized access to
42+
sensitive data stored in Vault, which makes incident response more
43+
straightforward.
44+
45+
## TLS resources
46+
47+
- [Default Vault TLS configuration](/vault/docs/configuration/listener/tcp#default-tls-configuration)
48+
- [Configure TLS for your Vault TCP listener](/vault/docs/configuration/listener/tcp/tcp-tls)
49+
- [Vault installation to minikube via Helm with TLS enabled](/vault/tutorials/kubernetes/kubernetes-minikube-tls)
50+
- [Medium blog: Enabling TLS on your Vault cluster on Kubernetes](https://medium.com/@martin.hodges/enabling-tls-on-your-vault-cluster-on-kubernetes-0d20439b13d0)

‎content/vault/v1.20.x/content/partials/ld-images/deploy/secure-vault-tls.mdx‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls-dark.png#dark-theme-only)
2+
![Secure Vault intra-cluster and inter-cluster communications with TLS](/img/diagram-secure-vault-tls.png#light-theme-only)

0 commit comments

Comments
 (0)