Namespace: (optional) an identifier of the Vault connection that must resolve the parameter. If a secret has multiple fields, but you don't specify a field name, Automation will try to get a field named value. If a secret has multiple fields, specify the field which value you want to get in an Automation job. For example, /aws/sts/mysecret.įield: (optional) a field name. Path: a Vault secret path in the Key/Value v1 or v2 secrets engine format. You will use this name to reference this variable in your scripts. On the project sidebar menu, choose Settings, then Secrets and Parameters. Vault namespace: (optional) a Vault namespace that is used in multi-tenant Vault configurations.Ĭlick Test connection and if connection is successfull, click Create. If a project has multiple Vault connections, Parameters namespace lets you specify which connection must be used to resolve a particular parameter. Parameters namespace: (optional) an additional connection identifier. Vault URL: a URL of the Vault server in the format.ĪppRole ID and AppRole Secret ID: credentials used by Space to log in to the Vault server. On the project sidebar menu, choose Settings, then Vault Connections.Ĭlick New connection and specify a connection Name and other settings: To configure connection to a Vault server The server stores secrets required by the build script. You have a working Vault server with a configured AppRole. Once you configure a connection to a Vault server, you can use variables from the storage the same way you use project parameters. In addition to its own secret storage, Space also supports external HashiCorp Vault storage. Val paramWithFallback = api.parameters ?: "fallback value" Vault parameters Container(displayName = "Get param value from env variable", image = "amazoncorretto:17-alpine").
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |