Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/helmfile/vals

Helm-like configuration values loader with support for various sources
https://github.com/helmfile/vals

Last synced: 21 days ago
JSON representation

Helm-like configuration values loader with support for various sources

Awesome Lists containing this project

README 

          
# vals



`vals` is a tool for managing configuration values and secrets.



It supports various backends including:



- Vault

- AWS SSM Parameter Store

- AWS Secrets Manager

- AWS S3

- GCP Secrets Manager

- GCP KMS

- [Google Sheets](#google-sheets)

- [SOPS](https://github.com/getsops/sops)-encrypted files

- Terraform State

- 1Password

- 1Password Connect

- [Doppler](https://doppler.com/)

- CredHub(Coming soon)

- Pulumi State

- Kubernetes

- Conjur

- HCP Vault Secrets

- Bitwarden

- [Yandex Cloud Lockbox](https://yandex.cloud/en/docs/lockbox/)

- Servercore Secrets Manager

- HTTP JSON

- Keychain

- Scaleway

- [Delinea SecretServer](https://delinea.com/products/secret-server)

- Infisical



- Use `vals eval -f refs.yaml` to replace all the `ref`s in the file to actual values and secrets.

- Use `vals exec -f env.yaml -- ` to populate envvars and execute the command.

- Use `vals env -f env.yaml` to render envvars that are consumable by `eval` or a tool like `direnv`



ToC:



- [Installation](#installation)

- [Usage](#usage)

  - [CLI](#cli)

  - [Helm](#helm)

  - [Go](#go)

- [Expression Syntax](#expression-syntax)

- [Supported Backends](#supported-backends)



## Installation



[![Packaging status](https://repology.org/badge/vertical-allrepos/vals.svg)](https://repology.org/project/vals/versions)



### Download binary (Linux, macOS, Windows)



[Download](https://github.com/helmfile/vals/releases) the latest executable for your platform and put it into a directory included in `PATH`.



### homebrew (macOS, Linux)



```sh

brew install vals

```



### Arch Linux



```sh

sudo pacman -S vals

```



### Alpine Linux Edge



```sh

apk add vals

```



### MacPorts (macOS)



```sh

sudo port install vals

```



### Nix / NixOS



```sh

nix profile install nixpkgs#vals

```



### Scoop (Windows)



```sh

scoop install vals

```



## Usage



- [CLI](#cli)

- [Helm](#helm)

- [Go](#go)



# CLI



```

vals is a Helm-like configuration "Values" loader with support for various sources and merge strategies



Usage:

  vals [command]



Available Commands:

  eval          Evaluate a JSON/YAML document and replace any template expressions in it and prints the result

  exec          Populates the environment variables and executes the command

  env           Renders environment variables to be consumed by eval or a tool like direnv

  get           Evaluate a string value passed as the first argument and replace any expressiosn in it and prints the result

  ksdecode      Decode YAML document(s) by converting Secret resources' "data" to "stringData" for use with "vals eval"

  version       Print vals version



Use "vals [command] --help" for more information about a comman

```



`vals` has a collection of providers that each an be referred with a URI scheme looks `ref+`.



For this example, use the [Vault](https://www.terraform.io/docs/providers/vault/index.html) provider.



Let's start by writing some secret value to `Vault`:



```console

$ vault kv put secret/foo mykey=myvalue

```



Now input the template of your YAML and refer to `vals`' Vault provider by using `ref+vault` in the URI scheme:



```console

$ VAULT_TOKEN=yourtoken VAULT_ADDR=http://127.0.0.1:8200/ \

  echo "foo: ref+vault://secret/data/foo?proto=http#/mykey" | vals eval -f -

```



Voila! `vals`, replacing every reference to your secret value in Vault, produces the output looks like:



```yaml

foo: myvalue

```



Which is equivalent to that of the following shell script:



```bash

VAULT_TOKEN=yourtoken  VAULT_ADDR=http://127.0.0.1:8200/ cat <::secret:/myteam/mydoc/?region=ap-southeast-2#/secret/key`



#### AWS S3



- `ref+s3://BUCKET/KEY/OF/OBJECT[?region=REGION&profile=AWS_PROFILE&role_arn=ASSUMED_ROLE_ARN&version_id=ID]`

- `ref+s3://BUCKET/KEY/OF/OBJECT[?region=REGION&profile=AWS_PROFILE&role_arn=ASSUMED_ROLE_ARN&version_id=ID]#/yaml_or_json_key/in/secret`



Examples:



- `ref+s3://mybucket/mykey`

- `ref+s3://mybucket/myjsonobj#/foo/bar`

- `ref+s3://mybucket/myyamlobj#/foo/bar`

- `ref+s3://mybucket/mykey?region=us-west-2`

- `ref+s3://mybucket/mykey?profile=prod`



#### AWS KMS



- `ref+awskms://BASE64CIPHERTEXT[?region=REGION&profile=AWS_PROFILE&role_arn=ASSUMED_ROLE_ARN&alg=ENCRYPTION_ALGORITHM&key=KEY_ID&context=URL_ENCODED_JSON]`

- `ref+awskms://BASE64CIPHERTEXT[?region=REGION&profile=AWS_PROFILE&role_arn=ASSUMED_ROLE_ARN&alg=ENCRYPTION_ALGORITHM&key=KEY_ID&context=URL_ENCODED_JSON]#/yaml_or_json_key/in/secret`



Decrypts the URL-safe base64-encoded ciphertext using AWS KMS. Note that URL-safe base64 encoding is

the same as "traditional" base64 encoding, except it uses `_` and `-` in place of `/` and `+`, respectively.

For example, to get a URL-safe base64-encoded ciphertext using the AWS CLI, you might run

```

aws kms encrypt \

  --key-id alias/example \

  --plaintext $(echo -n "hello, world" | base64 -w0) \

  --query CiphertextBlob \

  --output text |

  tr '/+' '_-'

```



Valid values for `alg` include:

* `SYMMETRIC_DEFAULT` (the default)

* `RSAES_OAEP_SHA_1`

* `RSAES_OAEP_SHA_256`



Valid value formats for `key` include:

* A key id `1234abcd-12ab-34cd-56ef-1234567890ab`

* A URL-encoded key id ARN: `arn%3Aaws%3Akms%3Aus-east-2%3A111122223333%3Akey%2F1234abcd-12ab-34cd-56ef-1234567890ab`

* A URL-encoded key alias: `alias%2FExampleAlias`

* A URL-encoded key alias ARN: `arn%3Aaws%3Akms%3Aus-east-2%3A111122223333%3Aalias%2FExampleAlias`



For ciphertext encrypted with a symmetric key, the `key` field may be omitted. For ciphertext

encrypted with a key in your own account, a plain key id or alias can be used. If the encryption

key is from another AWS account, you must use the key or alias ARN.



Use the `context` parameter to optionally specify the encryption context used when encrypting the

ciphertext. Format it by URL-encoding the JSON representation of the encryption context. For example,

if the encryption context is `{"foo":"bar","hello":"world"}`, then you would represent that as

`context=%7B%22foo%22%3A%22bar%22%2C%22hello%22%2C%22world%22%7D`.



Examples:

- `ref+awskms://AQICAHhy_i8hQoGLOE46PVJyinH...WwHKT0i3H0znHRHwfyC7AGZ8ek=`

- `ref+awskms://AQICAHhy...nHRHwfyC7AGZ8ek=#/foo/bar`

- `ref+awskms://AQICAHhy...WwHKT0i3AGZ8ek=?context=%7B%22foo%22%3A%22bar%22%2C%22hello%22%2C%22world%22%7D`

- `ref+awskms://AQICAVJyinH...WwHKT0iC7AGZ8ek=?alg=RSAES_OAEP_SHA1&key=alias%2FExampleAlias`

- `ref+awskms://AQICA...fyC7AGZ8ek=?alg=RSAES_OAEP_SHA256&key=arn%3Aaws%3Akms%3Aus-east-2%3A111122223333%3Akey%2F1234abcd-12ab-34cd-56ef-1234567890ab&context=%7B%22foo%22%3A%22bar%22%2C%22hello%22%2C%22world%22%7D`



#### Google GCS

- `ref+gcs://BUCKET/KEY/OF/OBJECT[?generation=ID]`

- `ref+gcs://BUCKET/KEY/OF/OBJECT[?generation=ID]#/yaml_or_json_key/in/secret`



Examples:



- `ref+gcs://mybucket/mykey`

- `ref+gcs://mybucket/myjsonobj#/foo/bar`

- `ref+gcs://mybucket/myyamlobj#/foo/bar`

- `ref+gcs://mybucket/mykey?generation=1639567476974625`



### GCP Secrets Manager



- `ref+gcpsecrets://PROJECT/SECRET[?version=VERSION]`

- `ref+gcpsecrets://PROJECT/SECRET[?version=VERSION]#/yaml_or_json_key/in/secret`

- `ref+gcpsecrets://PROJECT/SECRET[?version=VERSION][&fallback=valuewhenkeyisnotfound][&optional=true][&trim_nl=true]#/yaml_or_json_key/in/secret`



Examples:



- `ref+gcpsecrets://myproject/mysecret`

- `ref+gcpsecrets://myproject/mysecret?version=3`

- `ref+gcpsecrets://myproject/mysecret?version=3#/yaml_or_json_key/in/secret`



> NOTE: Got an error like `expand gcpsecrets://project/secret-name?version=1: failed to get secret: rpc error: code = PermissionDenied desc = Request had insufficient authentication scopes.`?

>

> In some cases like you need to use an alternative credentials or project,

> you'll likely need to set `GOOGLE_APPLICATION_CREDENTIALS` and/or `GCP_PROJECT` envvars.



If `GCP_PROJECT` environment variable is set, the project name can be omitted from the URI, like:



- `ref+gcpsecrets://mysecret`

- `ref+gcpsecrets://mysecret?version=3`



### GCP KMS



- `ref+gkms://BASE64CIPHERTEXT?project=myproject&location=global&keyring=mykeyring&crypto_key=mykey`

- `ref+gkms://BASE64CIPHERTEXT?project=myproject&location=global&keyring=mykeyring&crypto_key=mykey#/yaml_or_json_key/in/secret`



Decrypts the URL-safe base64-encoded ciphertext using GCP KMS. Note that URL-safe base64 encoding is the same as "traditional" base64 encoding, except it uses _ and - in place of / and +, respectively. For example, to get a URL-safe base64-encoded ciphertext using the GCP CLI, you might run

```

echo test | gcloud kms encrypt \

  --project myproject \

  --location global \

  --keyring mykeyring \

  --key mykey \

  --plaintext-file - \

  --ciphertext-file - \

  | base64 -w0 \

  | tr '/+' '_-'

```



### Google Sheets



- `ref+googlesheets://SPREADSHEET_ID?credentials_file=credentials.json#/KEY`



Examples:



- `ref+googlesheets://foobarbaz?credentials_file=credentials.json#/MYENV1` authenticates Google Sheets API using the credentials.json file, retrieve KVs from the sheet wit the spreadsheet ID "foobarbaz", and retrieves the value for the key "MYENV1". The `credentials.json` can be either a serviceaccount json key file, or client credentials file. In case it's a client credentials file, vals initiates a WebAuth flow and prints the URL. You open the URL with a browser, authenticate yourself there, copy the resulting auth code, input the auth code to vals.



### Terraform (tfstate)



- `ref+tfstate://relative/path/to/some.tfstate/RESOURCE_NAME[?aws_profile=AWS_PROFILE]`

- `ref+tfstate:///absolute/path/to/some.tfstate/RESOURCE_NAME[?aws_profile=AWS_PROFILE]`

- `ref+tfstate://relative/path/to/some.tfstate/RESOURCE_NAME[?az_subscription_id=AZ_SUBSCRIPTION_ID]`

- `ref+tfstate:///absolute/path/to/some.tfstate/RESOURCE_NAME[?az_subscription_id=AZ_SUBSCRIPTION_ID]`



Options:



`aws_profile`: If non-empty, `vals` tries to let tfstate-lookup to use the specified AWS profile defined in the well-known `~/.credentials` file.

`az_subscription_id`: If non-empty, `vals` tries to let tfstate-lookup to use the specified Azure Subscription ID.



Examples:



- `ref+tfstate://path/to/some.tfstate/aws_vpc.main.id`

- `ref+tfstate://path/to/some.tfstate/module.mymodule.aws_vpc.main.id`

- `ref+tfstate://path/to/some.tfstate/output.OUTPUT_NAME`

- `ref+tfstate://path/to/some.tfstate/data.thetype.name.foo.bar`



When you're using [terraform-aws-vpc](https://github.com/terraform-aws-modules/terraform-aws-vpc) to define a `module "vpc"` resource and you wanted to grab the first vpc ARN created by the module:



```

$ tfstate-lookup -s ./terraform.tfstate module.vpc.aws_vpc.this[0].arn

arn:aws:ec2:us-east-2:ACCOUNT_ID:vpc/vpc-0cb48a12e4df7ad4c



$ echo 'foo: ref+tfstate://terraform.tfstate/module.vpc.aws_vpc.this[0].arn' | vals eval -f -

foo: arn:aws:ec2:us-east-2:ACCOUNT_ID:vpc/vpc-0cb48a12e4df7ad4c

```



You can also grab a Terraform output by using `output.OUTPUT_NAME` like:



```

$ tfstate-lookup -s ./terraform.tfstate output.mystack_apply

```



which is equivalent to the following input for `vals`:



```

$ echo 'foo: ref+tfstate://terraform.tfstate/output.mystack_apply' | vals eval -f -

```



Remote backends like S3, GCS and AzureRM blob store are also supported. When a remote backend is used in your terraform workspace, there should be a local file at `./terraform/terraform.tfstate` that contains the reference to the backend:



```

{

    "version": 3,

    "serial": 1,

    "lineage": "f1ad69de-68b8-9fe5-7e87-0cb70d8572c8",

    "backend": {

        "type": "s3",

        "config": {

            "access_key": null,

            "acl": null,

            "assume_role_policy": null,

            "bucket": "yourbucketnname",

```



Just specify the path to that file, so that `vals` is able to transparently make the remote state contents available for you.



### Terraform in GCS bucket (tfstategs)



- `ref+tfstategs://bucket/path/to/some.tfstate/RESOURCE_NAME`



Examples:



- `ref+tfstategs://bucket/path/to/some.tfstate/google_compute_disk.instance.id`



It allows to use Terraform state stored in GCS bucket with the direct URL to it. You can try to read the state with command:



```

$ tfstate-lookup -s gs://bucket-with-terraform-state/terraform.tfstate google_compute_disk.instance.source_image_id

5449927740744213880

```



which is equivalent to the following input for `vals`:



```

$ echo 'foo: ref+tfstategs://bucket-with-terraform-state/terraform.tfstate/google_compute_disk.instance.source_image_id' | vals eval -f -

```



### Terraform in S3 bucket (tfstates3)



- `ref+tfstates3://bucket/path/to/some.tfstate/RESOURCE_NAME`



Examples:



- `ref+tfstates3://bucket/path/to/some.tfstate/aws_vpc.main.id`



It allows to use Terraform state stored in AWS S3 bucket with the direct URL to it. You can try to read the state with command:



```

$ tfstate-lookup -s s3://bucket-with-terraform-state/terraform.tfstate module.vpc.aws_vpc.this[0].arn

arn:aws:ec2:us-east-2:ACCOUNT_ID:vpc/vpc-0cb48a12e4df7ad4c

```



which is equivalent to the following input for `vals`:



```

$ echo 'foo: ref+tfstates3://bucket-with-terraform-state/terraform.tfstate/module.vpc.aws_vpc.this[0].arn' | vals eval -f -

```

### Terraform in AzureRM Blob storage (tfstateazurerm)



- `ref+tfstateazurerm://{resource_group_name}/{storage_account_name}/{container_name}/{blob_name}.tfstate/RESOURCE_NAME[?az_subscription_id=SUBSCRIPTION_ID]`



Examples:



- `ref+tfstateazurerm://my_rg/my_storage_account/terraform-backend/unique.terraform.tfstate/output.virtual_network.name`

- `ref+tfstateazurerm://my_rg/my_storage_account/terraform-backend/unique.terraform.tfstate/output.virtual_network.name?az_subscription_id=abcd-efgh-ijlk-mnop`



It allows to use Terraform state stored in Azure Blob storage given the resource group, storage account, container name and blob name. You can try to read the state with command:



```

$ tfstate-lookup -s azurerm://my_rg/my_storage_account/terraform-backend/unique.terraform.tfstate output.virtual_network.name

```



which is equivalent to the following input for `vals`:



```

$ echo 'foo: ref+tfstateazurerm://my_rg/my_storage_account/terraform-backend/unique.terraform.tfstate/output.virtual_network.name' | vals eval -f -

```



### Terraform in Terraform Cloud / Terraform Enterprise (tfstateremote)



- `ref+tfstateremote://app.terraform.io/{org}/{myworkspace}/RESOURCE_NAME`



Examples:



- `ref+tfstateremote://app.terraform.io/myorg/myworkspace/output.virtual_network.name`



It allows to use Terraform state stored in Terraform Cloud / Terraform Enterprise given the resource group, the organization and the workspace. You can try to read the state with command (with exported variable `TFE_TOKEN`):



```

$ tfstate-lookup -s remote://app.terraform.io/myorg/myworkspace output.virtual_network.name

```



which is equivalent to the following input for `vals`:



```

$ echo 'foo: ref+tfstateremote://app.terraform.io/myorg/myworkspace/output.virtual_network.name' | vals eval -f -

```



### SOPS



- The whole content of a SOPS-encrypted file: `ref+sops://base64_data_or_path_to_file?key_type=[filepath|base64]&format=[binary|dotenv|yaml]`

- The value for the specific path in an encrypted YAML/JSON document: `ref+sops://base64_data_or_path_to_file#/json_or_yaml_key/in/the_encrypted_doc`



Note: When using an inline base64-encoded sops "file", be sure to use URL-safe Base64 encoding.

URL-safe base64 encoding is the same as "traditional" base64 encoding, except it uses `_` and `-` in

place of `/` and `+`, respectively. For example, you might use the following command:

`sops -e <(echo "foo") | base64 -w0 | tr '/+' '_-'`



Examples:



- `ref+sops://path/to/file` reads `path/to/file` as `binary` input

- `ref+sops://?key_type=base64` reads `` as the base64-encoded data to be decrypted by sops as `binary`

- `ref+sops://path/to/file#/foo/bar` reads `path/to/file` as a `yaml` file and returns the value at `foo.bar`.

- `ref+sops://path/to/file?format=json#/foo/bar` reads `path/to/file` as a `json` file and returns the value at `foo.bar`.



### Keychain



Keychain provider is going to be available on macOS only. It reads a secret from the macOS Keychain.



- `ref+keychain://KEY1/[#/path/to/the/value]`



Examples:



- `security add-generic-password -U -a ${USER} -s "secret-name" -D "vals-secret" -w '{"foo":{"bar":"baz"}}'` - will create a secret in the Keychain with the name `secret-name` and the value `{"foo":{"bar":"baz"}}`, `vals-secret` is required to be able to find the secret in the Keychain.

- `echo 'foo: ref+keychain://secret-name' | vals eval -f -` - will read the secret from the Keychain with the name `secret-name` and replace the `foo` with the secret value.

- `echo 'foo: ref+keychain://secret-name#/foo/bar' | vals eval -f -` - will read the secret from the Keychain with the name `secret-name` and replace the `foo` with the value at the path `$.foo.bar`.



### Echo



Echo provider echoes the string for testing purpose. Please read [the original proposal](https://github.com/roboll/helmfile/pull/920#issuecomment-548213738) to get why we might need this.



- `ref+echo://KEY1/KEY2/VALUE[#/path/to/the/value]`



Examples:



- `ref+echo://foo/bar` generates `foo/bar`

- `ref+echo://foo/bar/baz#/foo/bar` generates `baz`. This works by the host and the path part `foo/bar/baz` generating an object `{"foo":{"bar":"baz"}}` and the fragment part `#/foo/bar` results in digging the object to obtain the value at `$.foo.bar`.



### File



File provider reads a local text file, or the value for the specific path in a YAML/JSON file.



- `ref+file://relative/path/to/file[#/path/to/the/value]`

- `ref+file:///absolute/path/to/file[#/path/to/the/value]`



Examples:



- `ref+file://foo/bar` loads the file at `foo/bar`

- `ref+file:///home/foo/bar` loads the file at `/home/foo/bar`

- `ref+file://foo/bar?encode=base64` loads the file at `foo/bar` and encodes its content to a base64 string

- `ref+file://some.yaml#/foo/bar` loads the YAML file at `some.yaml` and reads the value for the path `$.foo.bar`.

  Let's say `some.yaml` contains `{"foo":{"bar":"BAR"}}`, `key1: ref+file://some.yaml#/foo/bar` results in `key1: BAR`.



### Exec



Exec provider executes an arbitrary CLI command and uses its stdout as the secret value. This enables integration with any secrets backend that has a CLI tool, without needing a dedicated provider.



- `ref+exec://COMMAND[/ARG1/ARG2][?args=EXTRA1,EXTRA2&timeout=30&trim=true&env_KEY=VALUE][#/json/path]`



The command name is taken from the URI host, and path segments become positional arguments. Additional comma-separated arguments can be appended via the `args` query parameter. The command is executed directly (no shell invocation) for security.



Parameters:



| Parameter | Description | Default |

|---|---|---|

| `args` | Additional comma-separated arguments appended after path args | (none) |

| `timeout` | Execution timeout in seconds | `30` |

| `trim` | Trim trailing whitespace from stdout | `true` |

| `env_KEY` | Set environment variable `KEY` for the child process | (none) |



Examples:



- `ref+exec://echo/hello` — runs `echo hello`, returns `hello`

- `ref+exec://bw/get/password/item-id` — runs `bw get password item-id`

- `ref+exec://my-script.sh?args=--key,my-secret` — runs `my-script.sh --key my-secret`

- `ref+exec://vault-helper.sh?args=read,secret/db#/password` — runs the command, parses JSON/YAML output, and extracts `$.password`

- `ref+exec:///usr/local/bin/my-tool?args=fetch,key1` — absolute path command

- `ref+exec://my-tool?env_API_TOKEN=xyz&timeout=10` — sets env var `API_TOKEN=xyz` with 10s timeout



### Azure Key Vault



Retrieve secrets from Azure Key Vault. Path is used to specify the vault and secret name. Optionally a specific secret version can be retrieved.



- `ref+azurekeyvault://VAULT-NAME/SECRET-NAME[/VERSION]`



VAULT-NAME is either a simple name if operating in AzureCloud (vault.azure.net) or the full endpoint dns name when operating against non-default azure clouds (US Gov Cloud, China Cloud, German Cloud).

Examples:

- `ref+azurekeyvault://my-vault/secret-a`

- `ref+azurekeyvault://my-vault/secret-a/ba4f196b15f644cd9e949896a21bab0d`

- `ref+azurekeyvault://gov-cloud-test.vault.usgovcloudapi.net/secret-b`



#### Authentication



Vals acquires Azure credentials via the [azidentity Go module](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity).



By default, the following authentication types will be tried and the first one that works will be used:



1. [Environment Variables](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity#EnvironmentCredential)

1. [Workload Identity](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity#WorkloadIdentityCredential)

1. [Managed Identity](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity#ManagedIdentityCredential)

1. [Azure CLI](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity#AzureCLICredential)

1. [Azure Developer CLI](https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/azidentity#AzureDeveloperCLICredential)



In practice, the simplest way to authenticate is to log into the Azure CLI using an account that has access to read secrets from the Key Vault in question.



In case you are running in an environment that has multiple authentication types configured at once (and you need to use one that is lower on the list above), you can choose a specific one to use by setting the environment variable `AZKV_AUTH` to to one of the following values.



- Default Behavior: `default` (or unset)

- Workload Identity: `workload`

- Managed Identity: `managed`

- Azure CLI: `cli`

- Azure Developer CLI: `devcli`



### EnvSubst



Environment variables substitution.



- `ref+envsubst://$VAR1`



Examples:



- `ref+envsubst://$VAR1` loads environment variables `$VAR1`



### GitLab Secrets



For this provider to work you require an [access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) exported as the environment variable `GITLAB_TOKEN`.



- `ref+gitlab://my-gitlab-server.com/project_id/secret_name?[ssl_verify=false&scheme=https&api_version=v4]`



Examples:



- `ref+gitlab://gitlab.com/11111/password`

- `ref+gitlab://my-gitlab.org/11111/password?ssl_verify=true&scheme=https`



### 1Password



For this provider to work a working [service account token](https://developer.1password.com/docs/service-accounts/get-started/) is required.

The following env var has to be configured:

- `OP_SERVICE_ACCOUNT_TOKEN`



1Password is organized in vaults and items.

An item can have multiple fields with or without a section. Labels can be set on fields and sections.

Vaults, items, sections and labels can be accessed by ID or by label/name (and IDs and labels can be mixed and matched in one URL).



If a section does not have a label the field is only accessible via the section ID. This does not hold true for some default fields which may have no section at all (e.g.username and password for a `Login` item).



See [Secret reference syntax](https://developer.1password.com/docs/cli/secrets-reference-syntax/) for more information.



*Caution: vals-expressions are parsed as URIs. For the 1Password provider the host component of the URI identifies the vault. Therefore vaults containing certain characters not allowed in the host component (e.g. whitespaces, see [RFC-3986](https://www.rfc-editor.org/rfc/rfc3986#section-3.2.2) for details) can only be accessed by ID.*



Examples:



- `ref+op://VAULT_NAME/ITEM_NAME/FIELD_NAME`

- `ref+op://VAULT_ID/ITEM_NAME/FIELD_NAME`

- `ref+op://VAULT_NAME/ITEM_NAME/[SECTION_NAME/]FIELD_NAME`



### 1Password Connect



For this provider to work you require a working and accessible [1Password connect server](https://developer.1password.com/docs/connect).

The following env vars have to be configured:

- `OP_CONNECT_HOST`

- `OP_CONNET_TOKEN`



1Password is organized in vaults and items.

An item can have multiple fields with or without a section. Labels can be set on fields and sections.

Vaults, items, sections and labels can be accessed by ID or by label/name (and IDs and labels can be mixed and matched in one URL).



If a section does not have a label the field is only accessible via the section ID. This does not hold true for some default fields which may have no section at all (e.g.username and password for a `Login` item).



*Caution: vals-expressions are parsed as URIs. For the 1Password connect provider the host component of the URI identifies the vault (by ID or name). Therefore vaults containing certain characters not allowed in the host component (e.g. whitespaces, see [RFC-3986](https://www.rfc-editor.org/rfc/rfc3986#section-3.2.2) for details) can only be accessed by ID.*



Examples:



- `ref+onepasswordconnect://VAULT_ID/ITEM_ID#/[SECTION_ID.]FIELD_ID`

- `ref+onepasswordconnect://VAULT_LABEL/ITEM_LABEL#/[SECTION_LABEL.]FIELD_LABEL`

- `ref+onepasswordconnect://VAULT_LABEL/ITEM_ID#/[SECTION_LABEL.]FIELD_ID`



### Doppler



- `ref+doppler://PROJECT/ENVIRONMENT/SECRET_KEY[?token=dp.XX.XXXXXX&address=https://api.doppler.com&no_verify_tls=false&include_doppler_defaults=false]`



* `PROJECT` can be absent if the Token is a `Service Token` for that project. It can be set via `DOPPLER_PROJECT` envvar. See [Doppler docs](https://docs.doppler.com/docs/enclave-service-tokens) for more information.

* `ENVIRONMENT` (aka: "Config") can be absent if the Token is a `Service Token` for that project. It can be set via `DOPPLER_ENVIRONMENT` envvar. See [Doppler docs](https://docs.doppler.com/docs/enclave-service-tokens) for more information.

* `SECRET_KEY` can be absent and it will fetch all secrets for the project/environment.

* `token` defaults to the value of the `DOPPLER_TOKEN` envvar.

* `address` defaults to the value of the `DOPPLER_API_ADDR` envvar, if unset: `https://api.doppler.com`.

* `no_verify_tls` default `false`.

* `include_doppler_defaults` defaults to `false`, if set to `true` it will include the Doppler defaults for the project/environment (DOPPLER_ENVIRONMENT, DOPPLER_PROJECT and DOPPLER_CONFIG). It only works when `SECRET_KEY` is absent.



Examples:



(DOPPLER_TOKEN set as environment variable)



- `ref+doppler:////` fetches all secrets for the project/environment when using a Service Token.

- `ref+doppler:////FOO` fetches the value of secret with name `FOO` for the project/environment when using a Service Token.

- `ref+doppler://#FOO` fetches the value of secret with name `FOO` for the project/environment when using a Service Token.

- `ref+doppler://MyProject/development/DB_PASSWORD` fetches the value of secret with name `DB_PASSWORD` for the project named `MyProject` and environment named `development`.

- `ref+doppler://MyProject/development/#DB_PASSWORD` fetches the value of secret with name `DB_PASSWORD` for the project named `MyProject` and environment named `development`.



### Pulumi State



Obtain value in state pulled from Pulumi Cloud REST API:



- `ref+pulumistateapi://RESOURCE_TYPE/RESOURCE_LOGICAL_NAME/ATTRIBUTE_TYPE/ATTRIBUTE_KEY_PATH?project=PROJECT&stack=STACK`



* `RESOURCE_TYPE` is a Pulumi [resource type](https://www.pulumi.com/docs/concepts/resources/names/#types) of the form `::`, where forward slashes (`/`) are replaced by a double underscore (`__`) and colons (`:`) are replaced by a single underscore (`_`). For example `aws:s3:Bucket` would be encoded as `aws__s3__Bucket` and `kubernetes:storage.k8s.io/v1:StorageClass` would be encoded as `kubernetes_storage.k8s.io__v1_StorageClass`. To read Pulumi stack outputs, set the resource type to `pulumi_pulumi_Stack`.

* `RESOURCE_LOGICAL_NAME` is the [logical name](https://www.pulumi.com/docs/concepts/resources/names/#logicalname) of the resource in the Pulumi program. To read Pulumi stack outputs, set this to the project name followed by a hyphen, then the stack name.

* `ATTRIBUTE_TYPE` is either `outputs` or `inputs`.

* `ATTRIBUTE_KEY_PATH` is a [GJSON](https://github.com/tidwall/gjson/blob/master/SYNTAX.md) expression that selects the desired attribute from the resource's inputs or outputs per the chosen `ATTRIBUTE_TYPE` value. You must encode any characters that would otherwise not comply with URI syntax, for example `#` becomes `%23`.

* `project` is the Pulumi project name. May also be provided via the `PULUMI_PROJECT` environment variable.

* `stack` is the Pulumi stack name. May also be provided via the `PULUMI_STACK` environment variable.



Environment variables:



- `PULUMI_API_ENDPOINT_URL` is the Pulumi API endpoint URL. Defaults to `https://api.pulumi.com`. You may also provide this as the `pulumi_api_endpoint_url` query parameter.

- `PULUMI_ACCESS_TOKEN` is the Pulumi access token to use for authentication.

- `PULUMI_ORGANIZATION` is the Pulumi organization to use for authentication. You may also provide this as an `organization` query parameter.

- `PULUMI_PROJECT` is the Pulumi project. You may also provide this as a `project` query parameter.

- `PULUMI_STACK` is the Pulumi stack. You may also provide this as a `stack` query parameter.



Examples:



- `ref+pulumistateapi://aws-native_s3_Bucket/my-bucket/outputs/bucketName?project=my-project&stack=my-stack`

- `ref+pulumistateapi://aws-native_s3_Bucket/my-bucket/outputs/tags.%23(key==SomeKey).value?project=my-project&stack=my-stack`

- `ref+pulumistateapi://kubernetes_storage.k8s.io__v1_StorageClass/gp2-encrypted/inputs/metadata.name?project=my-project&stack=my-stack`

- `ref+pulumistateapi://pulumi_pulumi_Stack/project-name-stack-name/outputs/output-name?project=my-project&stack=my-stack`



### Kubernetes



Fetch value from Kubernetes:



- `ref+k8s://API_VERSION/KIND/NAMESPACE/NAME/KEY[?kubeConfigPath=&kubeContext=&inCluster]`



Authentication to the Kubernetes cluster is done by referencing the local kubeconfig file or in-cluster config.

The path to the kubeconfig can be specified as a URI parameter, read from the `KUBECONFIG` environment variable or the provider will attempt to read `$HOME/.kube/config`.

The Kubernetes context can be specified as a URI parameteter.

If `?inCluster` is passed in the URI, ensure the pod running the `vals`command has the appropriate RBAC permissions to access the ConfigMap/Secret.



Environment variables:



- `KUBECONFIG` contains the path to the Kubeconfig that will be used to fetch the secret.



Examples:



- `ref+k8s://v1/Secret/mynamespace/mysecret/foo`

- `ref+k8s://v1/ConfigMap/mynamespace/myconfigmap/foo`

- `ref+k8s://v1/Secret/mynamespace/mysecret/bar?kubeConfigPath=/home/user/kubeconfig`

- `ref+k8s://v1/Secret/mynamespace/mysecret/foo?inCluster`

- `secretref+k8s://v1/Secret/mynamespace/mysecret/baz`

- `secretref+k8s://v1/Secret/mynamespace/mysecret/baz?kubeContext=minikube`



> NOTE: This provider only supports kind "Secret" or "ConfigMap" in apiVersion "v1" at this time.



### Conjur



This provider retrieves the value of secrets stored in [Conjur](https://www.conjur.org/).

It's based on the https://github.com/cyberark/conjur-api-go lib.



The following env vars have to be configured:

- `CONJUR_APPLIANCE_URL`

- `CONJUR_ACCOUNT`

- `CONJUR_AUTHN_LOGIN`

- `CONJUR_AUTHN_API_KEY`



- `ref+conjur://PATH/TO/VARIABLE/CONJUR_SECRET_ID[?address=CONJUR_APPLIANCE_URL&account=CONJUR_ACCOUNT&login=CONJUR_AUTHN_LOGIN&apikey=CONJUR_AUTHN_API_KEY]`



Example:



- `ref+conjur://branch/variable_name`



### HCP Vault Secrets



This provider retrieves the value of secrets stored in [HCP Vault Secrets](https://developer.hashicorp.com/hcp/docs/vault-secrets).



It is based on the [HashiCorp Cloud Platform Go SDK](https://github.com/hashicorp/hcp-sdk-go) lib.



Environment variables:



- `HCP_CLIENT_ID`: The service principal Client ID for the HashiCorp Cloud Platform.

- `HCP_CLIENT_SECRET`: The service principal Client Secret for the HashiCorp Cloud Platform.

- `HCP_ORGANIZATION_ID`: (Optional) The organization ID for the HashiCorp Cloud Platform. It can be omitted. If "Organization Name" is set, it will be used to fetch the organization ID, otherwise the organization ID will be set to the first organization ID found.

- `HCP_ORGANIZATION_NAME`: (Optional) The organization name for the HashiCorp Cloud Platform to fetch the organization ID.

- `HCP_PROJECT_ID`: (Optional) The project ID for the HashiCorp Cloud Platform. It can be omitted. If "Project Name" is set, it will be used to fetch the project ID, otherwise the project ID will be set to the first project ID found in the provided organization.

- `HCP_PROJECT_NAME`: (Optional) The project name for the HashiCorp Cloud Platform to fetch the project ID.



Parameters:



Parameters are optional and can be passed as query parameters in the URI, taking precedence over environment variables.



- `client_id`: The service principal Client ID for the HashiCorp Cloud Platform.

- `client_secret`: The service principal Client Secret for the HashiCorp Cloud Platform.

- `organization_id`: The organization ID for the HashiCorp Cloud Platform. It can be omitted. If "Organization Name" is set, it will be used to fetch the organization ID, otherwise the organization ID will be set to the first organization ID found.

- `organization_name`: The organization name for the HashiCorp Cloud Platform to fetch the organization ID.

- `project_id`: The project ID for the HashiCorp Cloud Platform. It can be omitted. If "Project Name" is set, it will be used to fetch the project ID, otherwise the project ID will be set to the first project ID found in the provided organization.

- `project_name`: The project name for the HashiCorp Cloud Platform to fetch the project ID.

- `version`: The version digit of the secret to fetch. If omitted or fail to parse, the latest version will be fetched.



Example:



`ref+hcpvaultsecrets://APPLICATION_NAME/SECRET_NAME[?client_id=HCP_CLIENT_ID&client_secret=HCP_CLIENT_SECRET&organization_id=HCP_ORGANIZATION_ID&organization_name=HCP_ORGANIZATION_NAME&project_id=HCP_PROJECT_ID&project_name=HCP_PROJECT_NAME&version=2]`



### Bitwarden

This provider retrieves the secrets stored in Bitwarden. It uses the [Bitwarden Vault-Management API](https://bitwarden.com/help/vault-management-api/) that is included in the [Bitwarden CLI](https://github.com/bitwarden/clients) by executing `bw serve`.



Environment variables:



- `BW_API_ADDR`: The Bitwarden Vault Management API service address, defaults to http://localhost:8087



Parameters:



Parameters are optional and can be passed as query parameters in the URI, taking precedence over environment variables.



* `address` defaults to the value of the `BW_API_ADDR` envvar.



Examples:



- `ref+bw://4d084b01-87e7-4411-8de9-2476ab9f3f48` gets the password of the item id

- `ref+bw://4d084b01-87e7-4411-8de9-2476ab9f3f48/password` gets the password of the item id

- `ref+bw://4d084b01-87e7-4411-8de9-2476ab9f3f48/{username,password,uri,notes,item}` gets username, password, uri, notes or the whole item of the given item id

- `ref+bw://4d084b01-87e7-4411-8de9-2476ab9f3f48/notes#/key1` gets the *key1* from the yaml stored as note in the item



### Yandex Cloud Lockbox



Retrieve secrets from [Yandex Cloud Lockbox](https://yandex.cloud/en/docs/lockbox/). Path is used to specify secret ID. Optionally a specific secret version can be retrieved (using current version by default). If fragment is specified, retrieves a specific key from the secret.



- `ref+yclockbox://SECRET_ID[?version_id=VERSION][#KEY]`



Examples:



- `ref+yclockbox://e6qeoqvd88dcpf044n5i` - get whole secret `e6qeoqvd88dcpf044n5i` from the current version

- `ref+yclockbox://e6qeoqvd88dcpf044n5i?version_id=e6qn22seoaprg9cbe1dj` - get whole secret `e6qeoqvd88dcpf044n5i` from the `e6qn22seoaprg9cbe1dj` version

- `ref+yclockbox://e6qeoqvd88dcpf044n5i?version_id=e6qn22seoaprg9cbe1dj#oauth_secret` - get secret entry from the `oauth_secret` key of `e6qn22seoaprg9cbe1dj` version of `e6qeoqvd88dcpf044n5i` secret

- `ref+yclockbox://e6qeoqvd88dcpf044n5i#oauth_secret` - get secret entry from the `oauth_secret` key of current version of `e6qeoqvd88dcpf044n5i` secret



#### Authentication



Vals aquires Yandex Cloud IAM token from the `YC_TOKEN` environment variable. The easiest way to get it is to run `yc iam create-token`. See [Yandex Cloud Lockbox docs](https://yandex.cloud/en/docs/lockbox/api-ref/authentication) for more details on authentication



### HTTP JSON



This provider retrieves values stored in JSON hosted by a HTTP frontend.



This provider is built on top of [jsonquery](https://pkg.go.dev/github.com/antchfx/jsonquery@v1.3.3) and [xpath](https://pkg.go.dev/github.com/antchfx/xpath@v1.2.3) packages.



Given the diverse array of JSON structures that can be encountered, utilizing jsonquery with XPath presents a more effective approach for handling this variability in data structures.



This provider requires an xpath to be provided.



Do not include the protocol scheme i.e. http/https. Provider defaults to scheme https (http is available, see below)



Examples:



#### Fetch string value



`ref+httpjson:///?[insecure=false&floatAsInt=false]#/`



Let's say you want to fetch the below JSON object from https://api.github.com/users/helmfile/repos:

```json

[

    {

        "name": "chartify"

    },

    {

        "name": "go-yaml"

    }

]

```

```

# To get name="chartify" using https protocol you would use:

ref+httpjson://api.github.com/users/helmfile/repos#///*[1]/name



# To get name="go-yaml" using https protocol you would use:

ref+httpjson://api.github.com/users/helmfile/repos#///*[2]/name



# To get name="go-yaml" using http protocol you would use:

ref+httpjson://api.github.com/users/helmfile/repos?insecure=true#///*[2]/

```



#### Fetch integer value



`ref+httpjson:///?[insecure=false&floatAsInt=false]#/`



Let's say you want to fetch the below JSON object from https://api.github.com/users/helmfile/repos:

```json

[

    {

        "id": 251296379

    }

]

```

```

# Running the following will return: 2.51296379e+08

ref+httpjson://api.github.com/users/helmfile/repos#///*[1]/id



# Running the following will return: 251296379

ref+httpjson://api.github.com/users/helmfile/repos?floatAsInt=true#///*[1]/id

```



### Servercore secret manager



Retrieve secrets from Servercore Secrets Manager. The path identifies the secret. If a fragment is specified, the provider returns a specific key from the decoded secret.



Authentication:



Set the following environment variables:



- `SERVERCORE_USERNAME`

- `SERVERCORE_PASSWORD`

- `SERVERCORE_ACCOUNT_ID`

- `SERVERCORE_PROJECT_NAME`



URI formats:



- `ref+servercore://SECRET_NAME`

  Returns the secret value as a string.

- `ref+servercore://SECRET_NAME#/key/in/secret`

  Parses the decoded secret as JSON (with YAML as a fallback) and returns the value at the leaf key path.



Notes:

- The provider expects the Servercore API to return a base64-encoded string in the `version.value` field. After decoding, the provider attempts JSON parsing, and if that fails, YAML.

- API reference: [Servercore Secrets API](https://docs.servercore.com/api/secrets-manager-secrets/).



### Scaleway

This provider allows retrieval of secrets from [Scaleway Secret Manager](https://www.scaleway.com/en/docs/secret-manager/) using the [Scaleway Go SDK](https://github.com/scaleway/scaleway-sdk-go). For authentication, it uses the environment variables `SCW_PROJECT_ID` (defaults to `SCW_DEFAULT_PROJECT_ID` if unset), `SCW_REGION` (defaults to `SCW_DEFAULT_REGION` if unset), `SCW_ACCESS_KEY`, and `SCW_SECRET_KEY`. You can reference secrets in your config using the `ref+scw://` URI scheme.



Examples:



- `ref+scw:///path/to/secret` retrieves the value of an Opaque secret at the specified path.

- `ref+scw:///path/to/secret#key` retrieves the value for a specific key in a JSON secret at the specified path.



### Infisical



This provider allows retrieval of secrets from [Infisical](https://infisical.com) (either the SaaS or a self-deployment) using the [Infisical Go SDK](https://github.com/infisical/go-sdk).



Environment variables:



- `INFISICAL_URL`: the Infisical instance URL, defaults to the SaaS (`https://app.infisical.com`).

- `INFISICAL_AUTH_METHOD` (required): the authentication method, one of: `UNIVERSAL_AUTH`, `KUBERNETES`, `AWS_IAM`, `AZURE`, `GCP_IAM`, `GCP_ID_TOKEN`.



Parameters:



- `project` or `project_id` (required): the project slug or ID, respectively, where the secret lives in.

- `environment` (required): the slug name (`dev`, `prod`, etc) of the environment from where the secret should be fetched.

- `path`: the path from where the secret should be fetched.

- `type`: the type of the secret. Valid options are `shared` (default) or `personal`.

- `version`: the version of the secret to retrieve.



Examples:



- `ref+infisical://WEBHOOK_URL?project=infrastructure-hue8&path=prometheus&environment=prod`: gets the secret at "infrastructure-hue8" (project slug) -> "prometheus" (folder) -> "WEBHOOK_URL" (secret) -> "prod" (environment).

- `ref+infisical://POSTGRES_PASSWORD?project_id=c2f75015-37b7-40b6-8412-2523ddfea5ed&environment=dev`: gets the secret at "c2f75015-37b7-40b6-8412-2523ddfea5ed" (project ID) -> "POSTGRES_PASSWORD" (secret) -> "dev" (environment).



#### Authentication



These are the supported authentication methods. Please, read [the SDK docs](https://infisical.com/docs/sdks/languages/go#authentication) for more information.



Depending on which one is chosen with the `INFISICAL_AUTH_METHOD` environment variable, the following environment variables must also be provided.



- **Universal**: `UNIVERSAL_AUTH`

  - `INFISICAL_UNIVERSAL_AUTH_CLIENT_ID`: your machine identity client ID.

  - `INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET`: your machine identity client secret.

- **Kubernetes**: `KUBERNETES`

  - `INFISICAL_KUBERNETES_IDENTITY_ID`: your Infisical Machine Identity ID.

  - `INFISICAL_KUBERNETES_SERVICE_ACCOUNT_TOKEN_PATH`: the environment variable name that contains the path to the service account token (defaults to: `/var/run/secrets/kubernetes.io/serviceaccount/token`).

- **AWS IAM**: `AWS_IAM`

  - `INFISICAL_AWS_IAM_AUTH_IDENTITY_ID`: your Infisical Machine Identity ID.

- **Azure**: `AZURE`

  - `INFISICAL_AZURE_AUTH_IDENTITY_ID`: your Infisical Machine Identity ID.

- **GCP IAM**: `GCP_IAM`

  - `INFISICAL_GCP_IAM_AUTH_IDENTITY_ID`: your Infisical Machine Identity ID.

  - `INFISICAL_GCP_IAM_SERVICE_ACCOUNT_KEY_FILE_PATH`: the path to your GCP service account key file.

- **GCP ID Token**: `GCP_ID_TOKEN`

  - `INFISICAL_GCP_AUTH_IDENTITY_ID`: your Infisical Machine Identity ID.



### SecretServer



This provider allows retrieval of secrets from [Delinea SecretSever](https://delinea.com/products/secret-server) using their [REST API](https://docs.delinea.com/online-help/secret-server/api-scripting/rest-api/index.htm)



#### Configuration



For on-prem instances set `TSS_SERVER_URL`. For cloud use set `TSS_TLD` to the top level domain and `TSS_TENANT` to your tenant id. If `TSS_SERVER_URL` is set other connection variables are ignored.



#### Authentication



Authentication is done via environment variables:



- `TSS_USERNAME`: username to authenticate with

- `TSS_PASSWORD`: password to authenticate with

- `TSS_DOMAIN`: optional domain for the user



Alternatively you can provide an OAuth token directly via `TSS_TOKEN`. If you do all other authentication environment variables are ignored.



#### Parameters



You can disable ssl certificate verification by setting `ssl_verify=false` in the URLs

query.



#### Examples



- `ref+tss://12345#/password`: gets the `password` field of the secret with id `12345`

- `ref+tss://secret-name/password`: gets the `password` field of the secret with the name `secret-name`. The name has to uniquely identify the secret



#### Limitations



The content of file fields, like certificates can't be retrieved. They will be replaced with the string `*** Not Valid For Display ***`.



## Advanced Usages



### Discriminating config and secrets



`vals` has an advanced feature that helps you to do GitOps.



`GitOps` is a good practice that helps you to review how your change would affect the production environment.



To best leverage GitOps, it is important to remove dynamic aspects of your config before reviewing.



On the other hand, `vals`'s primary purpose is to defer retrieval of values until the time of deployment, so that we won't accidentally git-commit secrets. The flip-side of this is, obviously, that you can't review the values themselves.



Using `ref+` and `secretref+` in combination with `vals eval --exclude-secret` helps it.



By using the `secretref+` notation, you tell `vals` that it is a secret and regular `ref+` instances are for config values.



```yaml

myconfigvalue: ref+awsssm://myconfig/value

mysecretvalue: secretref+awssecrets://mysecret/value

```



To leverage `GitOps` most by allowing you to review the content of `ref+awsssm://myconfig/value` only, you run `vals eval --exclude-secret` to generate the following:



```yaml

myconfigvalue: MYCONFIG_VALUE

mysecretvalue: secretref+awssecrets://mysecret/value

```



This is safe to be committed into git because, as you've told to `vals`, `awsssm://myconfig/value` is a config value that can be shared publicly.



## Non-Goals



### Complex String-Interpolation / Template Functions



In the early days of this project, the original author has investigated if it was a good idea to introduce string interpolation like feature to vals:



```

foo: xx${{ref "ref+vault://127.0.0.1:8200/mykv/foo?proto=http#/mykey" }}

bar:

  baz: yy${{ref "ref+vault://127.0.0.1:8200/mykv/foo?proto=http#/mykey" }}

```



But the idea had abandoned due to that it seemed to drive the momentum to vals being a full-fledged YAML templating engine. What if some users started wanting to use `vals` for transforming values with functions?

That's not the business of vals.



Instead, use vals solely for composing sets of values that are then input to another templating engine or data manipulation language like Jsonnet and CUE.



Note though, `vals` does have support for simple string interpolation like usage. See [Expression Syntax](#expression-syntax) for more information.



### Merge



Merging YAMLs is out of the scope of `vals`. There're better alternatives like Jsonnet, Sprig, and CUE for the job.