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.

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

'Microsoft.CostManagement/scheduledActions' - ETag is required to update scheduled action #9393

Closed
vonbartas opened this issue Dec 28, 2022 · 1 comment

Comments

@vonbartas
Copy link

Bicep version
Bicep 0.13.1

The bicep creates a new resource (Anomaly report) but cannot update them.
I tried API's:
2022-10-01
2022-06-01-preview
2022-04-01-preview

Below Bicep module:

targetScope = 'subscription'

@description('Subscription id on which budget will be created')
param subscriptionId string

@description('Subscription Name')
param subscriptionName string

@description('Alert recipents')
param emailNotification array

param baseTime string = utcNow('u')

resource anomaliesReport 'Microsoft.CostManagement/scheduledActions@2022-10-01' = {
name: 'Dailyanomaly2'
kind: 'InsightAlert'
scope: subscription()
properties: {
displayName: 'Daily anomaly'
fileDestination: {
fileFormats: []
}
notificationEmail: ''
notification: {
message: 'Daily anomaly report'
subject: 'Cost anomaly detected in the ${subscriptionName} subscription'
to: emailNotification
}
schedule: {
endDate: dateTimeAdd(baseTime,'P1Y')
frequency: 'Daily'
startDate: baseTime
}
scope: 'subscriptions/${subscriptionId}'
status: 'Enabled'
viewId: resourceId('Microsoft.CostManagement/views/','ms:DailyAnomalyByResourceGroup')
}
}

@ghost ghost added the Needs: Triage 🔍 label Dec 28, 2022
@alex-frankel
Copy link
Collaborator

This is effectively a duplicate of Azure/bicep-types-az#1441 even though it is a different resource type. Recommendation is to open a support ticket so the Cost Management team can triage the issue.

@ghost ghost locked as resolved and limited conversation to collaborators May 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants