Admiral

Security

Secrets

Admiral resolves no secrets. Terraform code reads its own through ephemeral resources, and chart values pass through exactly as you wrote them.

Admiral works with the way you already handle secrets. A team that already reads secrets in its own module, or that already ships Sealed Secrets, External Secrets, or a Vault chart, keeps doing that. Admiral has no secret store and resolves no secret references.

How do I keep a secret out of Admiral?

In a Terraform component, read the secret in the code with an ephemeral resource and pass it to a write-only argument:

ephemeral "aws_secretsmanager_secret_version" "db" {
  secret_id = "arn:aws:secretsmanager:us-east-1:111122223333:secret:users-db"
}

resource "aws_db_instance" "users" {
  # ...
  password_wo         = ephemeral.aws_secretsmanager_secret_version.db.secret_string
  password_wo_version = 1
}

The provider reads the secret during plan and apply, with the cloud identity the agent runs the job with. Your secret manager decides which components can read which secrets. The value stays out of everything Admiral keeps:

  • The run artifact. When you plan, Admiral renders each component into a run artifact, the exact files the agent receives. The code names the secret, and the value is never in it.
  • The plan file. Apply runs the plan you reviewed, so the agent saves it with Admiral. A value from an ephemeral resource is not written into it.
  • Terraform state. A write-only argument is sent to the provider and never stored.

The other providers work the same way, for example google_secret_manager_secret_version (read secret_data) and vault_kv_secret_v2 (read data). This needs OpenTofu 1.11 or Terraform 1.11 or later, and a provider that offers the ephemeral resource and the write-only argument you use. Bump password_wo_version to send a rotated secret.

A module that takes a secret as an ordinary input variable cannot do this by itself. Wrap it in a module of your own that reads the secret ephemerally, or accept that the secret lands in state.

Can I put a secret in a value?

You can, and Admiral stores it as you wrote it. A Terraform engine also writes a variable's value into the saved plan file, even a variable marked sensitive, so a secret passed as a value lands in the plan file and, if the code stores it in an ordinary argument, in state. Read the secret in the code instead.

What happens to secrets in chart values?

A workload gets no secret resolution from Admiral. A chart's values are what the chart takes. Sealed Secrets ciphertext, an ExternalSecret name, a Vault wrapper, or plaintext you chose to put there all pass through untouched. Admiral does not refuse a chart and does not rewrite one.

Plaintext you put in values is stored as you gave it.

Which secrets still land in Terraform state?

A secret passed to an ordinary Terraform argument lands in state. This includes a value a resource computes, such as a generated password. An ephemeral value or a write-only argument stays out of it. The changeset review shows which arguments a plan marks sensitive.

When Admiral hosts the state, it encrypts it the way it encrypts a stored credential, and Admiral can decrypt it. When a component keeps its own backend, the secret lands in that backend, and Admiral never holds it.

Where to go next

On this page