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

Attribute "null_when_not_found" is not working and apply fails even after setting it as true #956

Closed
ksrijithjuniper opened this issue Oct 30, 2024 · 0 comments · Fixed by #959

Comments

@ksrijithjuniper
Copy link

Even after setting the attribute "null_when_not_found" in data apstra_datacenter_system as true, terraform apply fails with error Node not found.

Terraform provider version 0.74.0

Config :

learn the details of leaf1

data "apstra_datacenter_system" "ZAMN80121" {
blueprint_id = apstra_datacenter_blueprint.ZAM_DC1.id
name = "ZAMN80121"
null_when_not_found = true
}

Error message:

Error: Node not found

│ with data.apstra_datacenter_system.ZAMN80121,
│ on 02_blueprints.tf line 72, in data "apstra_datacenter_system" "ZAMN80121":
│ 72: data "apstra_datacenter_system" "ZAMN80121" {

│ Node with Name "ZAMN80121" not found in blueprint
│ "ab874390-8e50-4c9c-9d94-90726e8e1c18"

@bwJuniper bwJuniper linked a pull request Oct 30, 2024 that will close this issue
bwJuniper added a commit that referenced this issue Oct 30, 2024
…d-is-not-working-and-apply-fails-even-after-setting-it-as-true

Bug #956: honor`null_when_not_found` switch
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

Successfully merging a pull request may close this issue.

1 participant