Tom Harvey

@rkmanda any update on this one?

@ruowan see #19098 for the background - Service Team’s aren’t reviewing or responding to PR’s before the bot fires and it’s impacting/exerting effort for OSS contributors (who have to comment...

@ruowan perhaps the bot could be updated to ping the Service Team every 2 weeks instead, or a label as you've suggested to allow a team to manually work through...

@akning-ms > Based on Ruoxuan's comment, Should we close this PR. @tombuildsstuff Whilst I appreciate that @ruowan has been running a few of the PR's down, unfortunately this PR is...

@akning-ms unfortunately this issue isn't fixed, see the latest update in #19098

@ruowan I've seen a number of fixes closed over the years from both external contributors and Microsoft employees from this - so unfortunately this also affects PR's without the `customer-reported`...

@akning-ms @ruowan here's 3 more PRs, this time from Microsoft employees that are valid and fix real issues in the API (by updating the Swagger to reflect the API behaviour)...

@richeney > Ideally using the azurerm provider model would extend the set of functions with Azure specific functions - e.g. resourceid() - as well as the azurerm data sources and...

@BHoggs @richeney FWIW we've spent some time thinking about this recently, but unfortunately a generic Resource ID parsing function would quickly become problematic/a source of user configuration issues due the...

x-link: https://github.com/hashicorp/pandora/issues/2831