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

Service Connection Issues #27562

Open
1 task done
waynejnicklin opened this issue Oct 4, 2024 · 1 comment
Open
1 task done

Service Connection Issues #27562

waynejnicklin opened this issue Oct 4, 2024 · 1 comment

Comments

@waynejnicklin
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.

Terraform Version

1.7.5

AzureRM Provider Version

4.3.0

Affected Resource(s)/Data Source(s)

All

Terraform Configuration Files

n/a

Debug Output/Panic Output

n/a

Expected Behaviour

We intend to use an Azure DevOps service connection with read only access to the Azure resources, for our "plan" stage, and then a different Azure DevOps service connection with full write permissions for our "apply" stage. So in the pipeline tasks, we specify this, however, this doesn't seem to work, as it seems to embed the service connection details in the plan file, and then the apply stage fails with insufficient privileges, ignoring the service connection specified in the apply stage.

Actual Behaviour

We intend to use an Azure DevOps service connection with read only access to the Azure resources, for our "plan" stage, and then a different Azure DevOps service connection with full write permissions for our "apply" stage. So in the pipeline tasks, we specify this, however, this doesn't seem to work, as it seems to embed the service connection details in the plan file, and then the apply stage fails with insufficient privileges, ignoring the service connection specified in the apply stage.

Steps to Reproduce

n/a

Important Factoids

n/a

References

n/a

@waynejnicklin
Copy link
Author

Any updates on this?

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

No branches or pull requests

2 participants