-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add table azure_resource_health_emerging_issue #664
Comments
Hello @Lachlan-White, I apologize for the delayed response. We have created a preliminary pull request (PR) addressing this issue. Would you be willing to test it by switching to this branch ( To test the branch, follow these steps:
Your feedback would be greatly appreciated. Please let us know if the results meet your expectations or if you require any further assistance. Thank you! |
Hi @Lachlan-White , Did you get a chance to give it a try? |
Hello @Lachlan-White, have you had the opportunity to try it out yet? |
Closing this issue for now, we will revisit this once we have an update from the SDK issue. |
Reopening this Issue as the Azure SDK issue has been resolved and released a new version. |
@ParthaI @bigdatasourav @Lachlan-White closing this issue at the moment, since the scope of Azure SDK issue resolution involves a significant update to the Azure plugin's credential management code. We will revisit this issue once an SDK update is made at a larger scale, including addressing breaking changes 👍. |
References
Get API:
https://github.com/Azure/azure-sdk-for-go/blob/v58.0.0/services/resourcehealth/mgmt/2017-07-01/resourcehealth/emergingissues.go#L34
List API:
https://github.com/Azure/azure-sdk-for-go/blob/v58.0.0/services/resourcehealth/mgmt/2017-07-01/resourcehealth/emergingissues.go#L105
The text was updated successfully, but these errors were encountered: