Types of Secrets in CD-as-a-Service
Overview of using secrets with external systems
Secrets allow Armory CD-as-a-Service to authenticate with external systems and tools during a deployment.
You can store credentials for metrics providers like New Relic, DataDog, or Prometheus as secrets. Armory CD-as-a-Service uses these credentials to authenticate with your metric provider when querying for application metrics during a canary analysis.
You can store long-lived Kubernetes authentication tokens as secrets. Armory CD-as-a-Service uses these credentials to deploy, scale, and cache Kubernetes resources.
You can store GitHub Personal Access Tokens (PATs) as secrets. You can configure a webhook to authenticate with a GitHub PAT to kick off GitHub Actions-based integration tests during a deployment.
Secrets are encrypted in transit and at rest. They are additionally encrypted at rest with a per-tenant key using AES-256 encryption.
What’s nextCreate and Reference Secrets
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified October 27, 2022: (a80a18d)