Azure automation account is not displayed in either preview or create mode of the resource

[strangeronline]

Output from azd version
Run azd version and copy and paste the output here:

azd version
azd version 1.13.1 (commit 6f9ab45d9823cea818524eacfdb4210cc194d981)

Describe the bug
Azure automation account is not displayed in either preview or create mode of the resource

azd provision --no-state --no-prompt --preview

Previewing Azure resource changes (azd provision --preview)
This is a preview. No changes will be applied to your Azure resources.

Subscription: Visual Studio Enterprise Subscription – MPN (0f7da1c3-5989-4f75-9524-1d9c8a623c21)
Location: West Europe



SUCCESS: Generated provisioning preview in 21 seconds.

To Reproduce
Steps to reproduce the behavior...
Empty resource group or with an automation account altready exists

targetScope = 'resourceGroup'

resource automationAccount 'Microsoft.Automation/automationAccounts@2020-01-13-preview' = {
  name: 'automationAccounts'
  location: resourceGroup().location
  properties: {
    sku: {
      name: 'Basic'
    }
    publicNetworkAccess: true
  }
}

Expected behavior
if the resource exists: SKIP
if the resource not exists: CREATE

azd provision --no-state --preview

Previewing Azure resource changes (azd provision --preview)
This is a preview. No changes will be applied to your Azure resources.

Subscription: Visual Studio Enterprise Subscription – MPN (0f7da1c3-5989-4f75-9524-XXXXXXXX)
Location: West Europe

  Resources:

  Skip   : Automation Accounts    : automationAccounts

Environment
Information on your environment:
* Language name and version: bicep
* IDE and version : [e.g. Visual Studio 16.3] Visual Code

Additional context

When an automation account is created on the portal, it also does not generate a arm or bicep template

[Menghua1]

@rajeshkamal5050 This issue can be reproduced. After investigation, it is found that in the Preview() method, all resource types that do not have a defined display name are filtered out. For Microsoft.Automation/automationAccounts, because its display name is not defined in the in GetResourceTypeDisplayName(), so it is filtered out and not displayed in the preview output.

For the resource type Microsoft.Automation/automationAccounts, is it considered to be displayed? If so, I will open a PR to fix this issue by following the steps below:

1. In the constant definition section of the azure_resource_types.go file, add a new constant: AzureResourceTypeAutomationAccounts AzureResourceType = "Microsoft.Automation/automationAccounts".
2. In the GetResourceTypeDisplayName() function, add a new case: case AzureResourceTypeAutomationAccounts: return "Automation Accounts".

[Menghua1]

@strangeronline I tried to manually create an automation account on the portal and the deployment page is as follows. Is this the arm or bicep template you mentioned?

[strangeronline]

Peview of arm template absent at the create page

It becomes available only after real start of creation as seen in your picture.

[Menghua1]

Hi @rajeshkamal5050,

For the resource type Microsoft.Automation/automationAccounts, is it considered to be displayed in the provision output? If needed, we can submit a PR to support this. If not, we will close this issue.

Thanks!

[strangeronline]

Hi @rajeshkamal5050,

Why is it so difficult for you to make a decision? The issue was opened a month ago.

Thanks!

[Menghua1]

For the resource type Microsoft.Automation/automationAccounts, is it considered to be displayed in the provision output? If needed, we can submit a PR to support this. If not, we will close this issue.

@vhvb1989 Do you think Microsoft.Automation/automationAccounts should be included in the provision output?

[vhvb1989]

For the resource type Microsoft.Automation/automationAccounts, is it considered to be displayed in the provision output? If needed, we can submit a PR to support this. If not, we will close this issue.

@vhvb1989 Do you think Microsoft.Automation/automationAccounts should be included in the provision output?

Yes.
We don't have any rule about what resources should or which shouldn't be displayed in the output.
Folks would just open PRs when something expected is not defined yet.

Let me try to use the coding agent to add it. It should be straight fw. #5377