-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
[schedule_rotation] Allow "none" as rotation participant #61
[schedule_rotation] Allow "none" as rotation participant #61
Conversation
8b1b5ba
to
ccb4d4d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since "none" is a valid opsgenie schedule rotation type. we probably also need to add this to schedule_rotations
module, not just the config module
I belive there isn't a |
ccb4d4d
to
5210218
Compare
/terratest |
@Benbentwo was this a concurrency issue between PRs? |
Yeah looks like it Error: Error occurred with Status code: 409, Message: Escalation with [name] [escalation] already exists., Took: 0.047000, RequestId: b3972143-23bf-4085-8936-053989b8045f |
Going to squash and merge this, test looks like failure from conflicting names on tofu/terraform runs |
what
Allow "none" as a participant on a rotation.
why
This is a valid (and useful) value.
references
schedule_rotation opsgenie module