Skip to content

OpenAPI specs for Microsoft.Automation do not match information returned by /providers API #10662

@MWL88

Description

@MWL88

Based on the information returned by the AZ CLI (az providers list), resource provider Microsoft.Automation should expose resource type automationAccounts with the following API versions:

  • 2020-01-13-preview
  • 2019-06-01
  • 2018-06-30
  • 2018-01-15
  • 2017-05-15-preview
  • 2015-10-31
  • 2015-01-01-preview

The OpenAPI specs only defines resource type automationAccounts with the API version 2015-10-31

As a result, the auto-generated ARM template schema does not include the correct API versions and there is a conflict between the warnings reported by the arm-ttk and VS Code's ARM template schema validation ... as reported here Azure/arm-ttk#184

The OpenAPI spec definition is also not up to date for resource types:

  • automationAccounts/configurations
  • automationAccounts/webhooks
  • automationAccounts/softwareUpdateConfigurations
  • automationAccounts/jobs

Metadata

Metadata

Labels

AutomationService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions