This PR introduces a behaviour change when the integration key is missing from an entity configuration. Currently the behaviour is to disable the button but keep it on the screen.
After discussing the plugin with several customers, many shared with us that they don't want people to manually create incidents from Backstage as incidents are automatically created from alerts. Therefore we decided to remove the button if the integration key is not provided as part of the entity configuration, like we already do when the readonly parameter is passed to the PagerDutyCard.
This also allows us to save some valuable space in the PagerDutyCard.
Issue number: #67
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 a behaviour change when the
integration keyis missing from an entity configuration. Currently the behaviour is to disable the button but keep it on the screen.After discussing the plugin with several customers, many shared with us that they don't want people to manually create incidents from Backstage as incidents are automatically created from alerts. Therefore we decided to remove the button if the integration key is not provided as part of the entity configuration, like we already do when the
readonlyparameter is passed to the PagerDutyCard.This also allows us to save some valuable space in the PagerDutyCard.
Issue number: #67
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.