Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Warning

You have tried to access an archived page. Please go to the new https://root360.atlassian.net/wiki/spaces/KB to find more documents.

The root360 platform does provide a default set of environment variables already, e.g. details about other components (databases, cache layers, filesystems and so on) or the current environment (test, stage, prod, ….). Using those environment variables via install.sh you can configure your application with the appropriate endpoints of the environment.

You can enhance or extend this list of variables by adding new items yourself using the r3 suite. The content will be added to an encrypted vault inside AWS SecretsManager.

To verify the values on the targets you’re setting the secrets for, you can run sudo get-application-env (see here) on these roles.


Note

Variables already being provided by root360 can’t be overwritten.

Prerequisites

List Secrets

As the secrets scope is per role, you must provide a role parameter.

Code Block
~$ r3 secret list --role example
+----------------------+-----------------------------------------------+
|        Secret        |                     Value                     |
+----------------------+-----------------------------------------------+
| CUSTOMER_EXAMPLE_VAR | these-are-not-the-secrets-you-are-looking-for |
+----------------------+-----------------------------------------------+

Add/Update secrets

Secrets must be added/updated for a specific role and prefixed with CUSTOMER_.

Code Block
~$ r3 secret update --role example --name CUSTOMER_MYVAR --value "may-the-cloud-be-with-you"
2020-11-17 10:42:40 r3-11364 SUCCESS  Secret "CUSTOMER_MYVAR" successfully updated.
+----------------------+-----------------------------------------------+
|        Secret        |                     Value                     |
+----------------------+-----------------------------------------------+
| CUSTOMER_EXAMPLE_VAR | these-are-not-the-secrets-you-are-looking-for |
| CUSTOMER_MYVAR       | may-the-cloud-be-with-you                     |
+----------------------+-----------------------------------------------+

Delete secrets

Secrets must be deleted for a specific role.

Code Block
~$ r3 secret delete --role example --name CUSTOMER_MYVAR
2020-11-17 10:44:18 r3-11387 SUCCESS  Secret "CUSTOMER_MYVAR" successfully deleted.
+----------------------+-----------------------------------------------+
|        Secret        |                     Value                     |
+----------------------+-----------------------------------------------+
| CUSTOMER_EXAMPLE_VAR | these-are-not-the-secrets-you-are-looking-for |
+----------------------+-----------------------------------------------+

Recommended Articles

Filter by label (Content by label)
cqllabel in ( "deployment" , "r3" , "application" ) and type = "page" and space = "KB"

Status
colourYellow
titleintermediate

Table of Contents
exclude(Related questions|Table of contents).*