-
Notifications
You must be signed in to change notification settings - Fork 212
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
implementation of custom fields for terraform #623
implementation of custom fields for terraform #623
Conversation
ae55e13
to
89f1782
Compare
07c3f62
to
b254905
Compare
b254905
to
5d7a415
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.
@jedelson-pagerduty before proceeding with the merge, there are a few comments that need to be addressed please
Thanks for all the feedback @imjaroiswebdev . I think I've addressed all of these issues. |
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.
There are still a couple of comments to be addressed before merging @jedelson-pagerduty please 🙏🏽
pagerduty/resource_pagerduty_custom_field_schema_field_configuration.go
Outdated
Show resolved
Hide resolved
f850d9b
to
9989d43
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.
Awesome! Terraform managed Custom Fields will be loved by users. Thank you @jedelson-pagerduty 🎉 💪🏽 😎
This adds support for the new PagerDuty Custom Fields on Incidents features. These are currently in Early Access and not available to all accounts.
API Documentation for this feature are visible on https://developer.pagerduty.com/api-reference/f1a95bb9397ba-changelog
Dependent upon heimweh/go-pagerduty#120
Testing is done similarly to incident workflows where there is an environment variable (
PAGERDUTY_ACC_CUSTOM_FIELDS
) that must be set. As with workflows, any value will do, but1
is recommended: