feat: add sentry_organization_repository_azuredevops resource #293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've added a
sentry_organization_repository_azuredevops
resource, as I'm using this provider at work and need the ability to link our created projects to our Azure DevOps repositories. I would be very grateful if you could merge and release a new version with this addition.I based the code on the existing
sentry_organization_repository_github
and have tested it locally against our environment, which seems to work.The only issue I have spotted is that the resource seems to struggle with being destroyed for me, as it errors with the following:
The API token I was testing with was granted full access, so I'm not sure why it doesn't have permission. If I delete the repo manually via the Sentry dashboard I can see that the API call is made with the exact URL that Terraform tries to use, so the provider code seems to be correct. I don't know whether you are able to advise on what that could be. Even if we're unable to resolve that issue, I don't think it's necessarily a blocker for getting this merged.
Thanks