Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ProviderConfig Terraform State README #317

Open
dmlayton opened this issue Feb 6, 2025 · 1 comment
Open

ProviderConfig Terraform State README #317

dmlayton opened this issue Feb 6, 2025 · 1 comment

Comments

@dmlayton
Copy link

dmlayton commented Feb 6, 2025

Under "Known limitations" in the README it says:
You must either use remote state or ensure the provider container's /tf directory is not lost. provider-terraform does not persist state; consider using the [Kubernetes](https://www.terraform.io/docs/language/settings/backends/kubernetes.html) remote state backend.

But the default provider config includes:

 terraform {
      backend "kubernetes" {
        secret_suffix     = "providerconfig-aws-eu-west-1"
        namespace         = "upbound-system"
        in_cluster_config = true
      }
    }

Is this not doing just that? Is this part of the README wrong?

@bobh66
Copy link
Collaborator

bobh66 commented Feb 6, 2025

This is simply an example of a ProviderConfig - and in fact it's "wrong" if you are using the community version of Crossplane and not the Upbound version, since it has namespace "upbound-system" instead of "crossplane-system". The goal of the statement in the README is to ensure that it is clear that there is NO state persisted by default and you MUST ensure that the ProviderConfig(s) that you use include some sort of backend definition. Running with no backend defined will not work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants