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

BUG: Importing doppler_environment Ignores Enabled personal_configs #105

Open
tanakapayam opened this issue Oct 21, 2024 · 1 comment
Open

Comments

@tanakapayam
Copy link

Background

PR #92 added the ability to set personal_configs for doppler_environment, which is a beautiful thing.

Bug Report

I have a Doppler Environment, sandbox.dev, with the optional feature turned on, which I created previously via Doppler web console. After importing it, the plan step warns of the following change:

  # module.doppler-environment.doppler_environment.env["sandbox.dev"] will be updated in-place
  ~ resource "doppler_environment" "env" {
        id               = "sandbox.dev"
        name             = "Dev"
      + personal_configs = true
        # (2 unchanged attributes hidden)
    }

Expected Behavior

I expected to see:

No changes. Your infrastructure matches the configuration.

@nmanoogian
Copy link
Member

Thanks for reporting this! We'll dive in and take a look.

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

No branches or pull requests

2 participants