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

[Go] [Branch Protection] [Restrictions] unexpected result #147

Closed
dududko opened this issue Aug 4, 2021 · 1 comment
Closed

[Go] [Branch Protection] [Restrictions] unexpected result #147

dududko opened this issue Aug 4, 2021 · 1 comment
Assignees
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec resolution/wont-fix This issue won't be fixed

Comments

@dududko
Copy link

dududko commented Aug 4, 2021

While configuring the Restriction for a branch protection I have found multiple issues:

1) It is not possible to just enable the Restrictions without specifying Users, Apps or Teams. At least one user, team or app must be specified.

Screen Shot 2021-08-04 at 1 32 23 PM

I would like to just put this attribute to enable the Restrictions

			Restrictions: github.BranchProtectionV3RestrictionsArgs{},

2) If I specify at least one user the Restrictions are enabled

			Restrictions: github.BranchProtectionV3RestrictionsArgs{
				Users: pulumi.StringArray{
					pulumi.String("dududko"),
				},
			},

image

3) If I remove the user it is removed from github restrictions list, but the Restrictions itself is still enabled. There is no way to disable restrictions with pulumi after it is enabled.

@dududko dududko added the kind/enhancement Improvements or new features label Aug 4, 2021
@stack72 stack72 added kind/bug Some behavior is incorrect or out of spec and removed kind/enhancement Improvements or new features labels Aug 6, 2021
@mjeffryes
Copy link
Member

Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it?

@mjeffryes mjeffryes added the awaiting-feedback Blocked on input from the author label Sep 26, 2024
@mjeffryes mjeffryes added the resolution/wont-fix This issue won't be fixed label Oct 25, 2024
@mjeffryes mjeffryes self-assigned this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec resolution/wont-fix This issue won't be fixed
Projects
None yet
Development

No branches or pull requests

3 participants