This PR introduces the capability of replacing the Escalation Policy ID input in the 'pagerduty:service:create' action with a drop-down with the Escalation Policies available to the user. It does so by exposing a local API that gets all escalation policies and returns a list of names and ids.
It introduces a new configuration option (apiToken) documented as part of Backstage configuration schema. Without it the plugin is unable to start but I have implemented proper warnings and error message to warn the users. It is also documented in the official documentation.
Issue number: #2
Type of change
[x] New feature (non-breaking change which adds functionality)
[ ] Fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Description
This PR introduces the capability of replacing the Escalation Policy ID input in the 'pagerduty:service:create' action with a drop-down with the Escalation Policies available to the user. It does so by exposing a local API that gets all escalation policies and returns a list of names and ids.
It introduces a new configuration option (apiToken) documented as part of Backstage configuration schema. Without it the plugin is unable to start but I have implemented proper warnings and error message to warn the users. It is also documented in the official documentation.
Issue number: #2
Type of change
Checklist
If this is a breaking change 👇
Acknowledgement
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.