Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Include Azure Automation rest api version 2020-01-13-preview #15020

Closed
OmnipotentOwl opened this issue Jul 8, 2021 · 6 comments
Closed

Include Azure Automation rest api version 2020-01-13-preview #15020

OmnipotentOwl opened this issue Jul 8, 2021 · 6 comments
Assignees
@Alancere
Labels
Automation customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@OmnipotentOwl
Copy link

Service Package Request

Hello,

In investigating the ability to support Managed Identities on Azure Automation Accounts in Terraform it looks like the support which was last updated in the Azure Rest API specs repo with Azure/azure-rest-api-specs/pull/12928 never made it into the Azure SDK for Go repo but the PR for it did get auto-created #14309 but was not moved forward for some reason.

Currently, this is blocking the ability to implement Managed Identities for Azure Automation Accounts via hashicorp/terraform-provider-azurerm/issues/11503 and would further unblock this scenario for the Cloud Adoption Framework for Azure - Terraform landing zones module and solutions group via aztfmod/terraform-azurerm-caf/issues/474.

I would like to get be able to move forward with adding this support to Terraform so getting this new API version included would be greatly appreciated.
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jul 8, 2021
@doherty100
Copy link

Microsoft is recommending that customers stop using RunAs accounts for Azure Automation and move to managed identities so support for this is critical.

@RickWinter RickWinter added Automation Mgmt This issue is related to a management-plane library. labels Jul 19, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jul 19, 2021
@ArcturusZhang
Copy link
Member

Hey @OmnipotentOwl and @doherty100 thanks for this issue and sorry for the delay of response.

We have an internal email to confirm the readiness of their swagger, once we get that, we will release a new package for this api-version of this RP

@ArcturusZhang ArcturusZhang added feature-request This issue requires a new behavior in the product in order be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jul 23, 2021
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jul 23, 2021
@lirenhe
Copy link
Member

lirenhe commented Sep 10, 2021

We need to release a new version of the SDK for this.

@Alancere
Copy link
Contributor

Hi @OmnipotentOwl thanks for this issue!

Releasing a new package will require the service to submit a new SDK release request, I have added the label on this issue so that the corresponding service team could take this a look.
I also sent some internal emails to the contact of the corresponding service team about this.

@Alancere Alancere added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 13, 2021
@ghost
Copy link

ghost commented Sep 13, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @zjalexander.

Issue Details

Service Package Request

Hello,

In investigating the ability to support Managed Identities on Azure Automation Accounts in Terraform it looks like the support which was last updated in the Azure Rest API specs repo with Azure/azure-rest-api-specs/pull/12928 never made it into the Azure SDK for Go repo but the PR for it did get auto-created #14309 but was not moved forward for some reason.

Currently, this is blocking the ability to implement Managed Identities for Azure Automation Accounts via hashicorp/terraform-provider-azurerm/issues/11503 and would further unblock this scenario for the Cloud Adoption Framework for Azure - Terraform landing zones module and solutions group via aztfmod/terraform-azurerm-caf/issues/474.

I would like to get be able to move forward with adding this support to Terraform so getting this new API version included would be greatly appreciated.

Author: OmnipotentOwl
Assignees: ArcturusZhang
Labels:

Automation, Service Attention, Mgmt, customer-reported, needs-team-attention, feature-request
Milestone: -

@swupdiedoowap swupdiedoowap mentioned this issue Dec 2, 2021
Closed
@lirenhe lirenhe assigned Alancere and unassigned ArcturusZhang Dec 24, 2021
@Alancere
Copy link
Contributor

released in https://github.com/Azure/azure-sdk-for-go/tree/main/services/preview/automation/mgmt/2020-01-13-preview/automation

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Alancere Alancere

Labels
Automation customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@OmnipotentOwl @doherty100 @RickWinter @lirenhe @ArcturusZhang @Alancere