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

Error when running terraform apply with project using imported mist_org (.alarmtemplate_id) #74

Open
mwalter416 opened this issue Jan 29, 2025 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@mwalter416
Copy link

mwalter416 commented Jan 29, 2025

Describe the bug

Error when running terraform apply with project using imported mist_org

To Reproduce

Steps to reproduce the behavior:

  1. Import existing mist_org object to tf. (terraform import mist_org.cadenza_demo_pool <uuid>)
  2. Use this org with the "Getting started" How To
  3. terraform apply

Expected behavior

Successful Apply

Error Message

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to mist_org.cadenza_demo_pool, provider "provider[\"registry.terraform.io/juniper/mist\"]" produced an unexpected new value:
│ .alarmtemplate_id: was null, but now cty.StringVal("<UUID HERE>").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Software

Terraform v1.10.5
on darwin_arm64

  • provider registry.terraform.io/juniper/mist v0.2.18

Additional context

Add any other context about the problem here.

@mwalter416 mwalter416 added the bug Something isn't working label Jan 29, 2025
tmunzer added a commit that referenced this issue Jan 29, 2025
@tmunzer
Copy link
Collaborator

tmunzer commented Jan 29, 2025

Hi @mwalter416 ,

There was an issue on how to unset the "alarmtemplate_id" attrbiute in the org resource.
This has been fixed and will be added into the next release.

Regards
Thomas

@tmunzer tmunzer added this to the v0.2.19 milestone Feb 12, 2025
@tmunzer
Copy link
Collaborator

tmunzer commented Feb 14, 2025

Hi @mwalter416 ,

I just released v0.2.19 which is fixing this issue.
If you have time can you test and confirm this has been fixed?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants