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

Fix issue with disabling a ruleset #282

Merged

Conversation

divbhasin
Copy link
Contributor

Fixes #250.

There are 2 main changes here:

  • I added to the 2 existing ruleset_rule tests. Now, we first create a ruleset rule that has disabled=true, and then we update the same ruleset rule to disabled=false. This helps verify that we can go from true -> false, which was an issue before according to pagerduty_ruleset_rule - cannot set disabled=true once disabled=false was set #250. We still get the verification of creating and updating ruleset rules that we had before.

  • There was a change I made to the go-pagerduty client to enable this to work here. Thus, I needed to vendor the go-pagerduty repo, which also grabbed some other updates to the client.

@divbhasin divbhasin marked this pull request as ready for review November 18, 2020 15:54
@divbhasin divbhasin force-pushed the 250-change-disabled-behaviour branch from 5479aa4 to a8060d4 Compare November 18, 2020 20:56
Copy link
Contributor

@stmcallister stmcallister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! thank you for submitting this fix!

@stmcallister stmcallister merged commit 76520f7 into PagerDuty:master Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pagerduty_ruleset_rule - cannot set disabled=true once disabled=false was set
2 participants