-
Notifications
You must be signed in to change notification settings - Fork 777
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
feat: Enable custom protection rule on GH environment #2352
base: main
Are you sure you want to change the base?
Conversation
@kfcampbell Could you please review this PR, getting it merged and released would be really helpful for my team? |
@kfcampbell Can you take a look at this? would really help simplify my current workflow |
@ishan11 As a workaround until officially supported by the provider, are you using |
We ended up using a Rest API TF Provider but u think using a null resource with local exec would be fine as well |
@ishan11 could you rebase this PR and update the |
@stevehipwell both have been completed. |
@ishan11 do you think it might be useful to also add the corresponding data source? |
When can we expect this feature to be released ? It's an important feature we are looking for. |
@stevehipwell |
@ishan11 I'm not a maintainer, just a contributor. But it looks like the REST API would support data sources and given the lead time on a PR review it'd probably be best to bundle the work together. |
@stevehipwell Sorry, just getting back around to this topic. I went and did some more research on implementing the corresponding data resource. I was able to remember the issue that I was facing when originally trying to implement. According to the GitHub API docs this is the endpoint that will List custom deployment rule integrations available for an environment, which we could use to return a list object that contains the Sorry for the long winded answer and hopefully my statement above makes sense. I am open to ideas on what might be the best way to implement this |
Ok, I was able to come up with a solution that combines using two different APIs. Essentially it will merge the list of available integrations and already applied integrations so that whenever the datasource is called it won't show drift. @kfcampbell Could you please take a look this one? |
Resolves #2225
Before the change?
After the change?
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!
Testing Results