6576c2f15f
For some reason Terraform decided that it would otherwise like to *delete* this configuration, which is undesirable. Note that there is a "magic" special behaviour when the `alias` and `provider_id` are set to the name of a built-in supported provider (github, gitlab etc.), which lets us skip the authorization_url setup. Change-Id: Ib66154c2896dda162c57bdc2d7964a9fa4e15f20 Reviewed-on: https://cl.tvl.fyi/c/depot/+/6706 Tested-by: BuildkiteCI Reviewed-by: lukegb <lukegb@tvl.fyi> |
||
---|---|---|
.. | ||
.gitignore | ||
clients.tf | ||
default.nix | ||
main.tf | ||
README.md | ||
user_sources.tf |
Terraform for Keycloak
This contains the Terraform configuration for deploying TVL's Keycloak
instance (which lives at auth.tvl.fyi
).
Secrets are needed for applying this. The encrypted file
//ops/secrets/tf-keycloak.age
contains export
calls which should
be sourced, for example via direnv
, by users with the appropriate
credentials.
An example direnv
configuration used by tazjin is this:
# //ops/keycloak/.envrc
source_up
eval $(age --decrypt -i ~/.ssh/id_ed25519 $(git rev-parse --show-toplevel)/ops/secrets/tf-keycloak.age)