Azure / Azure/azure-rest-api-specs
Azure Automation Account requires state
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
This is a duplicate of [950](https://github.com/pulumi/pulumi-azure-native/issues/950#issue-930061817) as requested by @mikhailshilkov.
If I try to run up an Integration Account using the sample code from the Pulumi website (below) I get an error
error: autorest/azure: Service returned an error. Status=400 Code="InvalidIntegrationAccount" Message="The provided integration account definition is not valid."
## Steps to reproduce
"Pulumi up" the following code
```
using Pulumi;
using AzureNative = Pulumi.AzureNative;
class MyStack : Stack
{
public MyStack()
{
var integrationAccount = new AzureNative.Logic.IntegrationAccount("integrationAccount", new AzureNative.Logic.IntegrationAccountArgs
{
IntegrationAccountName = "testIntegrationAccount",
Location = "westus",
ResourceGroupName = "testResourceGroup",
Sku = new AzureNative.Logic.Inputs.IntegrationAccountSkuArgs
{
Name = "Standard",
},
});
}
}
```
The fix is to add a State property e.g. State = "Enabled" so I think this property needs to be marked as required and the documentation updated.
Cheers
Alan
Contributor guide
Research direction
Start by reviewing the linked issue 950, then inspect the Azure Logic IntegrationAccount definition and its State property. Reproduce the failure with the C# sample and verify that the specification marks the required state and that the published documentation reflects it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100