Open robnotley opened 9 months ago
Hi @robnotley. Thanks for letting us know about this issue. The html_url
field id described as:
It doesn't look like it should be equivalent to the "Integration URL" displayed in the web UI. I believe that you are doing the correct thing vis a vis concatenation.
I don't believe that integration_key
is being deprecated as an output, just as an input. We shouldn't be issuing the warning when you use it as an output. That is a bug.
What happened?
We have created a Microsoft Azure integration within PagerDuty. However the value for the webhook _htmlurl is incorrect so cannot be used. Instead we have to use the _integrationkey value and concat this into a static url. The _integrationkey value is due to be deprecated.
Example
PagerDuty Azure Integration Creation
Example output of pd_integration values
Please note that the _htmlurl value does not correspond to the Integration URL value shown in PagerDuty portal
Work Around
We are currently using the following as a workaround where we use a static url and concat the _integrationkey into the url.
However we receive the following warning when running pulumi up
_warning: integrationkey is deprecated: Assignments or updates to this attribute are not supported by Service Integrations API, it is a read-only value. Input support will be dropped in upcomming major release
Output of
pulumi about
Plugins NAME VERSION azure 5.41.0 azure-native 2.25.0 azuread 5.47.0 keycloak 5.2.1 mailgun 3.4.0 opsgenie 1.1.6 pagerduty 4.3.1 python unknown random 4.8.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).