Skip to content

Commit 3501b41

Browse files
authored
resolve merge conflict (#5716)
1 parent b172f38 commit 3501b41

File tree

1 file changed

+2
-8
lines changed
  • website/source/guides/integrations/vault-integration

1 file changed

+2
-8
lines changed

website/source/guides/integrations/vault-integration/index.html.md

+2-8
Original file line numberDiff line numberDiff line change
@@ -261,18 +261,12 @@ Nomad Server's configuration file located at `/etc/nomad.d/nomad.hcl`. Provide
261261
the token you generated in the previous step in the `vault` stanza of your Nomad
262262
server configuration. The token can also be provided as an environment variable
263263
called `VAULT_TOKEN`. Be sure to specify the `nomad-cluster-role` in the
264-
<<<<<<< HEAD:website/source/guides/operations/vault-integration/index.html.md
265-
[create_from_role][create-from-role] option. After following these steps and
266-
enabling Vault, the `vault` stanza in your Nomad server configuration will be
267-
similar to what is shown below:
268-
=======
269-
[create_from_role][create-from-role] option. If using
270-
[Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces/index.html),
264+
[create_from_role][create-from-role] option. If using [Vault
265+
Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces/index.html),
271266
modify both the client and server configuration to include the namespace;
272267
alternatively, it can be provided in the environment variable `VAULT_NAMESPACE`.
273268
After following these steps and enabling Vault, the `vault` stanza in your Nomad
274269
server configuration will be similar to what is shown below:
275-
>>>>>>> ac76fc2fd... Merge pull request #5667 from hashicorp/yishan/revised-nomadproject-structure:website/source/guides/integrations/vault-integration/index.html.md
276270

277271
```hcl
278272
vault {

0 commit comments

Comments
 (0)