import group doesn't set scope

[drdamour]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and Azure DevOps Provider) Version

Affected Resource(s)

• azuredevops_group

Terraform Configuration Files

resource "azuredevops_group" "crush" {
  scope        = azuredevops_project.opsys.id
  display_name = "Crush"
  description  = <<-EOF


    Managed by TF
EOF

}

Debug Output

Panic Output

Expected Behavior

after importing an immediate apply should not recreate the resource do to scope being altered

Actual Behavior

tf plan shows that a scope is causing a forced replacement

Steps to Reproduce

import a project scoped group then tf plan it.

1. terraform apply

Important Factoids

Removing the scope stanza from TF makes the replace go away...so i think when refreshing state it's not checking the scope either as omitting the scope stanza probably should show a problem

modifying the state file with the scope makes the replacement go away too as expected.

References

[xuzhang3]

Hi @drdamour Thanks for your feedback. The scope is the query parameter, should not be used to check the resource difference, I have submit a PR #347 to fix this issue.

[xuzhang3]

Close this issue, feel free to open another issue if you have questions.

[drdamour]

@xuzhang3 i'm not sure this was fixed, using 0.1.5 i'm now getting

[gdud]

I have the same issue as @drdamour in version 0.1.5 ...

Scope is set to null in a state file.

[xuzhang3]

@gdud Are you trying create a new group or import a group? can you share your configuration?

[drdamour]

@xuzhang3 i just had a need to do this again..and it's still and issue using 0.1.7

i import he group,then when i go to apply i get force replacement because of scope. in the state file it's empty

[drdamour]

can we reopen this plz

[Annesars90]

What is the status on this issue? I'm also getting the same problem. This is my process to test:

• Deploy a new group with terraform (incl scope).
• Remove group from tf state so it only exists is DevOps
• Import group to tf state, which leads to scope = null in the statefile
• Trying to redeploy group forces replacement because of scope

[xuzhang3]

@Annesars90 fixed in #519 . This scope is used to get the scope descriptor and the scope descriptor will not return by service, this property should not be compared during the plan/apply