Open slavizh opened 2 years ago
Seeing the same behaviour on Microsoft.CostManagement/views@2021-10-01
:
if you provide the eTag
after resource has been created: "Could not find member 'eTag' on object of type 'TemplateResource'. Path 'properties.template.resources[0].eTag'"
if you don't provide the eTag
: "Etag value required for update operation of view:
same old: we did the bare minimum on API and released it without testing ARM template support.
I am also facing similar issue. When I tried to create a resource group. Below is my bicep code.
targetScope = 'subscription'
param namePrefix string param envPrefix string param instaneID string param resourceLocation string = deployment().location param projectName string = 'SampleProject'
resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' = { name: '${namePrefix}-${projectName}-${envPrefix}-${instaneID}' location: resourceLocation tags: { Project: projectName InnovationsLab: 'InnovationsLab' Environment: envPrefix } }
Error Error from Azure portal : The request content was invalid and could not be deserialized: 'Could not find member 'etag' on object of type 'TemplateResource'. Path 'properties.template.resources[0].etag', line 1, position 1162.'. Any help is much appreciated.
I have the same issue, the API is not idempotent. In Azure/bicep#9393 you said to open a support ticket but this is not a solution, and Azure/bicep-types-az#1441 redirects here. Please reopen this issue.
Re-open which issue? Azure/bicep#9393 is closed as a duplicate because the resolution will be the same. This is an issue with the cost management API, so that is why we suggest a support ticket. We have made the cost management team aware of the issue and we hope the fix the issue soon, but we can't do anything beyond that. A support ticket is an effective way to get the issue in front of the team where they will need to provide a mitigation or ETA for a fix.
i just yesterday re-deployed 'Microsoft.CostManagement/scheduledActions@2022-10-01
multiple times with Bicep without getting any issues => looks like Azure/bicep#9393 is fixed on RP now.
But Bicep documentation of the given resource still has false information of about etag property: https://learn.microsoft.com/en-us/azure/templates/microsoft.costmanagement/scheduledactions?pivots=deployment-language-bicep. REST API also have similar mentions: https://learn.microsoft.com/en-us/rest/api/cost-management/scheduled-actions/create-or-update?tabs=HTTP
I did not test if direct API call to PUT https://management.azure.com/providers/Microsoft.CostManagement/scheduledActions/{name}?api-version=2022-10-01
still requires eTag but Bicep re-deployment is working.
@slavizh It could be a good idea to test if they fixed all API endpoints in their namespace
cc: @massimosil @alex-frankel
i just yesterday re-deployed
'Microsoft.CostManagement/scheduledActions@2022-10-01
multiple times with Bicep without getting any issues => looks like Azure/bicep#9393 is fixed on RP now.But Bicep documentation of the given resource still has false information of about etag property: https://learn.microsoft.com/en-us/azure/templates/microsoft.costmanagement/scheduledactions?pivots=deployment-language-bicep. REST API also have similar mentions: https://learn.microsoft.com/en-us/rest/api/cost-management/scheduled-actions/create-or-update?tabs=HTTP
I did not test if direct API call to
PUT https://management.azure.com/providers/Microsoft.CostManagement/scheduledActions/{name}?api-version=2022-10-01
still requires eTag but Bicep re-deployment is working.@slavizh It could be a good idea to test if they fixed all API endpoints in their namespace
cc: @massimosil @alex-frankel
It's fixed, I can confirm.
Awesome that this is fixed! I will move this into the types repo to track the swagger fix to mark etag as optional -- FYI @flanakin
I am confirming that idempotency is fixed in Microsoft.CostManagement/exports@2022-10-01 but Microsoft.CostManagement/views@2022-10-01 reported by another user still requires eTag thus still not ARM/Bicep Template compliant resource.
I will make a fair comment here that Cost Management team cannot write proper APIs. Even some of the newer and simple APIs like providers/Microsoft.CostManagement/settings do not work properly with ARM/Bicep Templates.
Not to mention also the API versions that are published but not available on the service thus you get that the API is not supported and message which are available ones.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ccmaxpcrew. Please see https://aka.ms/biceptypesinfo for troubleshooting help.
Author: | slavizh |
---|---|
Assignees: | - |
Labels: | `inaccuracy`, `RP: Microsoft.CostManagement`, `Service Attention`, `Cost Management and Consumption` |
Milestone: | - |
Hi, does the issue with Microsoft.CostManagement/views endpoint was resolved? Currently I'm facing this issue.
Hi, does the issue with Microsoft.CostManagement/views endpoint was resolved? Currently I'm facing this issue.
For me works fine.
Thank you @vonbartas. Can you confirm that *_eTag: ''_** should work? Which API version do you use?
Maybe you can find other reason why I'm getting message 'Could not find member 'eTag' on object of type 'TemplateResource'.
resource costAnomalyView 'Microsoft.CostManagement/views@2022-10-05-preview' = { name: vName eTag: '*' properties: { accumulated: 'string' chart: 'Table' displayName: 'CostAnomaly' metric: 'ActualCost' query: { dataSet: { aggregation: { totalCost: { function: 'Sum' name: 'PreTaxCost' } } granularity: 'Daily' grouping: [ { name: 'SubscriptionId' type: 'Dimension' } ] sorting: [ { direction: 'Descending' name: 'Subscription' } ] } includeMonetaryCommitment: null timeframe: 'WeekToDate' type: 'Usage' } scope: 'subscriptions/{subscriptionId}' } }
Thank you @vonbartas. Can you confirm that *_eTag: ''_** should work? Which API version do you use?
Maybe you can find other reason why I'm getting message 'Could not find member 'eTag' on object of type 'TemplateResource'.
resource costAnomalyView 'Microsoft.CostManagement/views@2022-10-05-preview' = { name: vName eTag: '*' properties: { accumulated: 'string' chart: 'Table' displayName: 'CostAnomaly' metric: 'ActualCost' query: { dataSet: { aggregation: { totalCost: { function: 'Sum' name: 'PreTaxCost' } } granularity: 'Daily' grouping: [ { name: 'SubscriptionId' type: 'Dimension' } ] sorting: [ { direction: 'Descending' name: 'Subscription' } ] } includeMonetaryCommitment: null timeframe: 'WeekToDate' type: 'Usage' } scope: 'subscriptions/{subscriptionId}' } }
@2022-10-01
unfortunatelly this API version also returns error "The request content was invalid and could not be deserialized: 'Could not find member 'eTag' on object of type 'TemplateResource' :(
@. @.> - AXP team was added on this thread instead of your team.
Sent from Outlookhttp://aka.ms/weboutlook
From: przlwo @.> Sent: Friday, October 27, 2023 4:04 AM To: Azure/bicep-types-az @.> Cc: BAFS Crew @.>; Mention @.> Subject: Re: [Azure/bicep-types-az] @.*** not idempotent (Issue #1441)
unfortunatelly this API version also returns error "The request content was invalid and could not be deserialized: 'Could not find member 'eTag' on object of type 'TemplateResource' :(
— Reply to this email directly, view it on GitHubhttps://github.com/Azure/bicep-types-az/issues/1441#issuecomment-1782721516, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUYECDFMSIIY5DBJYWOK6FDYBOIKJAVCNFSM6AAAAAAWD2R6TOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSG4ZDCNJRGY. You are receiving this because you were mentioned.Message ID: @.***>
--_000DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Sent from
Outlook
unfortunatelly this API version also returns error "Th= e request content was invalid and could not be deserialized: 'Could not fin= d member 'eTag' on object of type 'TemplateResource' :(
=97
Reply to this email directly,
view it on GitHub, or
unsubscribe.
You are receiving this because you were mentioned.Message
ID: <Azure/bicep-types-az/issues/1441/1782721516@github.com>
--_000DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp--
--_009DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 30 Oct 2023 18:31:59 GMT"; modification-date="Mon, 30 Oct 2023 18:32:50 GMT"
Received: from DS7PR21MB3054.namprd21.prod.outlook.com (2603:10b6:8:72::17) by
DS7PR21MB3669.namprd21.prod.outlook.com with HTTPS; Fri, 27 Oct 2023 11:04:09
+0000
Received: from DM6PR00CA0048.namprd00.prod.outlook.com (2603:10b6:5:331::17)
by DS7PR21MB3054.namprd21.prod.outlook.com (2603:10b6:8:72::17) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.11; Fri, 27 Oct
2023 11:04:05 +0000
Received: from SA2PEPF0000224F.namprd00.prod.outlook.com
(2603:10b6:5:331:cafe::63) by DM6PR00CA0048.outlook.office365.com
(2603:10b6:5:331::17) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6972.0 via Frontend
Transport; Fri, 27 Oct 2023 11:04:05 +0000
Authentication-Results: spf=pass (sender IP is 192.30.252.211)
smtp.mailfrom=github.com; dkim=pass (signature was verified)
header.d=github.com;dmarc=pass action=none
header.from=github.com;compauth=pass reason=100
Received-SPF: Pass (protection.outlook.com: domain of github.com designates
192.30.252.211 as permitted sender) receiver=protection.outlook.com;
client-ip=192.30.252.211; helo=out-28.smtp.github.com; pr=C
Received: from out-28.smtp.github.com (192.30.252.211) by
SA2PEPF0000224F.mail.protection.outlook.com (10.167.242.103) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6982.0 via Frontend Transport; Fri, 27 Oct 2023 11:04:05 +0000
Received: from github.com (hubbernetes-node-4258e3c.ash1-iad.github.net [10.56.200.22])
by smtp.github.com (Postfix) with ESMTPA id AACCF1003C0
for @.>; Fri, 27 Oct 2023 04:04:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2023; t=1698404644;
bh=ILcoewVsmmjsEUWTPMV7nCo7ulhse52kqVy5cHu/Ekk=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=DC9PkLBslSHP6xzhj3oivvxoMrc76PBQVPKe4Q77/L0kWPohtmvRVjy8uIq+ABsRD
ET2gZYJERcSl9BPGYxo7s21wE9RGoN/Qf6uYR6cEhspz8r9RIinHlgRSsNSIiBJ/3c
zHsbEREB0vCa0PF+QANYHIZ1wgz4qFz6qUlycmL8=
Date: Fri, 27 Oct 2023 04:04:04 -0700
From: przlwo @.>
Reply-To: Azure/bicep-types-az @.>
To: Azure/bicep-types-az @.>
Cc: ccmaxpcrew @.>,
Mention @.>
Message-ID: @.>
In-Reply-To: @.>
References: @.>
Subject: Re: [Azure/bicep-types-az]
@. not idempotent (Issue #1441)
Content-Type: multipart/alternative;
boundary="--==_mimepart_653b9924a7ec675d8045496";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: przlwo
X-GitHub-Recipient: ccmaxpcrew
X-GitHub-Reason: mention
List-ID: Azure/bicep-types-az
----==_mimepart_653b9924a7ec6_75d8045496 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
unfortunatelly this API version also returns error "The request content was invalid and could not be deserialized: 'Could not find member 'eTag' on object of type 'TemplateResource' :(
-- Reply to this email directly or view it on GitHub: https://github.com/Azure/bicep-types-az/issues/1441#issuecomment-1782721516 You are receiving this because you were mentioned.
Message ID: @.***> ----==_mimepart_653b9924a7ec6_75d8045496 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
unfortunatelly this API version also returns error "The request content was invalid and could not be deserialized: 'Could not find member 'eTag' on object of type 'TemplateResource' :(
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
----==_mimepart_653b9924a7ec6_75d8045496--
--_009DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 30 Oct 2023 18:31:59 GMT"; modification-date="Mon, 30 Oct 2023 18:32:50 GMT"
Received: from BL1PR21MB3088.namprd21.prod.outlook.com (2603:10b6:208:390::20)
by DS7PR21MB3669.namprd21.prod.outlook.com with HTTPS; Fri, 27 Oct 2023
06:55:27 +0000
Received: from DM6PR00CA0057.namprd00.prod.outlook.com (2603:10b6:5:331::26)
by BL1PR21MB3088.namprd21.prod.outlook.com (2603:10b6:208:390::20) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6954.11; Fri, 27 Oct
2023 06:55:22 +0000
Received: from DM3NAM06FT011.Eop-nam06.prod.protection.outlook.com
(2603:10b6:5:331:cafe::87) by DM6PR00CA0057.outlook.office365.com
(2603:10b6:5:331::26) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6973.0 via Frontend
Transport; Fri, 27 Oct 2023 06:55:22 +0000
Authentication-Results: spf=pass (sender IP is 192.30.252.209)
smtp.mailfrom=github.com; dkim=pass (signature was verified)
header.d=github.com;dmarc=pass action=none
header.from=github.com;compauth=pass reason=100
Received-SPF: Pass (protection.outlook.com: domain of github.com designates
192.30.252.209 as permitted sender) receiver=protection.outlook.com;
client-ip=192.30.252.209; helo=out-26.smtp.github.com; pr=C
Received: from out-26.smtp.github.com (192.30.252.209) by
DM3NAM06FT011.mail.protection.outlook.com (10.152.109.1) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6954.11 via Frontend Transport; Fri, 27 Oct 2023 06:55:22 +0000
Received: from github.com (hubbernetes-node-faef37f.ash1-iad.github.net [10.56.208.56])
by smtp.github.com (Postfix) with ESMTPA id D654E600049
for @.>; Thu, 26 Oct 2023 23:55:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2023; t=1698389721;
bh=PNuDK3FJkcqT/pSnh9hzJaKcMHHn+KsPbeNb/l2oX2w=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=B9BN40N4efmW9R8HrIc3FxwPiEizXuHOH74ip7NNoAIaRjp5IfEkKXUHSscgwhg+t
zpuC9NYVPAcLdpmDAfQIdp7oSx2hXZxlmwafu/OAAarhRTnZDGaBkKG48A9QK/WsBM
1SDA96J+wEleAgBs0F4l7BI+OIFKpxsX7YCj9Qkk=
Date: Thu, 26 Oct 2023 23:55:21 -0700
From: vonbartas @.>
Reply-To: Azure/bicep-types-az @.>
To: Azure/bicep-types-az @.>
Cc: ccmaxpcrew @.>,
Mention @.>
Message-ID: @.>
In-Reply-To: @.>
References: @.>
Subject: Re: [Azure/bicep-types-az]
@. not idempotent (Issue #1441)
Content-Type: multipart/alternative;
boundary="--==_mimepart_653b5ed9d319c94d8041232f3";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: vonbartas
X-GitHub-Recipient: ccmaxpcrew
X-GitHub-Reason: mention
List-ID: Azure/bicep-types-az
----==_mimepart_653b5ed9d319c_94d8041232f3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Thank you @vonbartas. Can you confirm that *_eTag: ''_** should work? Which API version do you use?
Maybe you can find other reason why I'm getting message 'Could not find member 'eTag' on object of type 'TemplateResource'.
resource costAnomalyView @.**' = { name: vName eTag: '' properties: { accumulated: 'string' chart: 'Table' displayName: 'CostAnomaly' metric: 'ActualCost' query: { dataSet: { aggregation: { totalCost: { function: 'Sum' name: 'PreTaxCost' } } granularity: 'Daily' grouping: [ { name: 'SubscriptionId' type: 'Dimension' } ] sorting: [ { direction: 'Descending' name: 'Subscription' } ] } includeMonetaryCommitment: null timeframe: 'WeekToDate' type: 'Usage' } scope: 'subscriptions/{subscriptionId}' } }
@2022-10-01
-- Reply to this email directly or view it on GitHub: https://github.com/Azure/bicep-types-az/issues/1441#issuecomment-1782395518 You are receiving this because you were mentioned.
Message ID: @.***> ----==_mimepart_653b5ed9d319c_94d8041232f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Thank you . Can you confirm that eTag: '*' should work? Which API version do you use?
Maybe you can find other reason why I'm getting message 'Could not find member 'eTag' on object of type 'TemplateResource'.
resource costAnomalyView ***@***.***' = { name: vName eTag: '*' properties: { accumulated: 'string' chart: 'Table' displayName: 'CostAnomaly' metric: 'ActualCost' query: { dataSet: { aggregation: { totalCost: { function: 'Sum' name: 'PreTaxCost' } } granularity: 'Daily' grouping: [ { name: 'SubscriptionId' type: 'Dimension' } ] sorting: [ { direction: 'Descending' name: 'Subscription' } ] } includeMonetaryCommitment: null timeframe: 'WeekToDate' type: 'Usage' } scope: 'subscriptions/{subscriptionId}' } }
<p @.***
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
----==_mimepart_653b5ed9d319c_94d8041232f3--
--_009DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 30 Oct 2023 18:31:59 GMT"; modification-date="Mon, 30 Oct 2023 18:32:50 GMT"
Received: from IA1PR21MB3473.namprd21.prod.outlook.com (2603:10b6:208:3e2::17)
by DS7PR21MB3669.namprd21.prod.outlook.com with HTTPS; Thu, 26 Oct 2023
13:26:53 +0000
Received: from MN2PR00CA0004.namprd00.prod.outlook.com (2603:10b6:208:224::17)
by IA1PR21MB3473.namprd21.prod.outlook.com (2603:10b6:208:3e2::17) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6954.5; Thu, 26 Oct
2023 13:26:46 +0000
Received: from BL2NAM06FT016.Eop-nam06.prod.protection.outlook.com
(2603:10b6:208:224:cafe::36) by MN2PR00CA0004.outlook.office365.com
(2603:10b6:208:224::17) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6951.0 via Frontend
Transport; Thu, 26 Oct 2023 13:26:46 +0000
Authentication-Results: spf=pass (sender IP is 192.30.252.211)
smtp.mailfrom=github.com; dkim=pass (signature was verified)
header.d=github.com;dmarc=pass action=none
header.from=github.com;compauth=pass reason=100
Received-SPF: Pass (protection.outlook.com: domain of github.com designates
192.30.252.211 as permitted sender) receiver=protection.outlook.com;
client-ip=192.30.252.211; helo=out-28.smtp.github.com; pr=C
Received: from out-28.smtp.github.com (192.30.252.211) by
BL2NAM06FT016.mail.protection.outlook.com (10.152.107.20) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6954.9 via Frontend Transport; Thu, 26 Oct 2023 13:26:45 +0000
Received: from github.com (hubbernetes-node-8312bd3.ash1-iad.github.net [10.56.201.101])
by smtp.github.com (Postfix) with ESMTPA id 7FF9C101172
for @.>; Thu, 26 Oct 2023 06:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2023; t=1698326805;
bh=uV4Te1MqfKpy7BUWQ2gcaAgQsVEj8SLvB53we2ynPmA=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=QIA0gPE+RTvA46ebg4CNsNrJSPEbwqud02wsZTuqepzhZvq9z9YOCCoSQD71CBcI4
ujCJbbCER12BK4gbUKG9qP+guOWakElilFCHKgJTuk5wXe4fTjEKJQJDGb2Rb8OgND
836TP1Uf59XXqFCkw21hoHg+fLpDoE4k++wgl3sQ=
Date: Thu, 26 Oct 2023 06:26:45 -0700
From: przlwo @.>
Reply-To: Azure/bicep-types-az @.>
To: Azure/bicep-types-az @.>
Cc: ccmaxpcrew @.>,
Mention @.>
Message-ID: @.>
In-Reply-To: @.>
References: @.>
Subject: Re: [Azure/bicep-types-az]
@. not idempotent (Issue #1441)
Content-Type: multipart/alternative;
boundary="--==_mimepart_653a69157d74687d8041304ab";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: przlwo
X-GitHub-Recipient: ccmaxpcrew
X-GitHub-Reason: mention
List-ID: Azure/bicep-types-az
----==_mimepart_653a69157d746_87d8041304ab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Thank you @vonbartas. Can you confirm that *_eTag: ''_** should work? Which API version do you use?
-- Reply to this email directly or view it on GitHub: https://github.com/Azure/bicep-types-az/issues/1441#issuecomment-1781124200 You are receiving this because you were mentioned.
Message ID: @.***> ----==_mimepart_653a69157d746_87d8041304ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Thank you .
Can you confirm that eTag: '*' should work? Which API version do you use?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
----==_mimepart_653a69157d746_87d8041304ab--
--_009DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 30 Oct 2023 18:32:00 GMT"; modification-date="Mon, 30 Oct 2023 18:32:50 GMT"
Received: from SJ1PR21MB3554.namprd21.prod.outlook.com (2603:10b6:a03:452::17)
by DS7PR21MB3669.namprd21.prod.outlook.com with HTTPS; Thu, 26 Oct 2023
13:18:29 +0000
Received: from DM6PR00CA0031.namprd00.prod.outlook.com (2603:10b6:5:114::44)
by SJ1PR21MB3554.namprd21.prod.outlook.com (2603:10b6:a03:452::17) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6954.8; Thu, 26 Oct
2023 13:18:25 +0000
Received: from DM3NAM06FT008.Eop-nam06.prod.protection.outlook.com
(2603:10b6:5:114:cafe::b6) by DM6PR00CA0031.outlook.office365.com
(2603:10b6:5:114::44) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6973.0 via Frontend
Transport; Thu, 26 Oct 2023 13:18:25 +0000
Authentication-Results: spf=pass (sender IP is 192.30.252.200)
smtp.mailfrom=github.com; dkim=pass (signature was verified)
header.d=github.com;dmarc=pass action=none
header.from=github.com;compauth=pass reason=100
Received-SPF: Pass (protection.outlook.com: domain of github.com designates
192.30.252.200 as permitted sender) receiver=protection.outlook.com;
client-ip=192.30.252.200; helo=out-17.smtp.github.com; pr=C
Received: from out-17.smtp.github.com (192.30.252.200) by
DM3NAM06FT008.mail.protection.outlook.com (10.152.108.103) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6954.9 via Frontend Transport; Thu, 26 Oct 2023 13:18:25 +0000
Received: from github.com (hubbernetes-node-6415157.va3-iad.github.net [10.48.206.55])
by smtp.github.com (Postfix) with ESMTPA id D0C684118A
for @.>; Thu, 26 Oct 2023 06:18:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2023; t=1698326304;
bh=LKtFODSc4BnCs/Eblp4wTPDtr54QR/uR5WCp18VksZ0=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=mHmtMazc3sKxQNwx2my2oa43A0NBf+vWIPT//gNYNoMDpG5qSChiEBBBO32JXy9Aj
Ft93tqPc3R7pbLAvQpHixMaF72hpC5LFALdOnW6zVn7voIdV4JjunRJLb1YT90YRU0
uyCGvjguHSloFos1kt8Z9pfcjnkgbj2OFBTPqIfI=
Date: Thu, 26 Oct 2023 06:18:24 -0700
From: vonbartas @.>
Reply-To: Azure/bicep-types-az @.>
To: Azure/bicep-types-az @.>
Cc: ccmaxpcrew @.>,
Mention @.>
Message-ID: @.>
In-Reply-To: @.>
References: @.>
Subject: Re: [Azure/bicep-types-az]
@. not idempotent (Issue #1441)
Content-Type: multipart/alternative;
boundary="--==_mimepart_653a6720c511874d8041108ed";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: vonbartas
X-GitHub-Recipient: ccmaxpcrew
X-GitHub-Reason: mention
List-ID: Azure/bicep-types-az
----==_mimepart_653a6720c5118_74d8041108ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Hi, does the issue with Microsoft.CostManagement/views endpoint was resolved? Currently I'm facing this issue.
For me works fine.
-- Reply to this email directly or view it on GitHub: https://github.com/Azure/bicep-types-az/issues/1441#issuecomment-1781108327 You are receiving this because you were mentioned.
Message ID: @.***> ----==_mimepart_653a6720c5118_74d8041108ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Hi, does the issue with Microsoft.CostManagement/views endpoint was resolved? Currently I'm facing this issue.
For me works fine.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
----==_mimepart_653a6720c5118_74d8041108ed--
--_009DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 30 Oct 2023 18:32:00 GMT"; modification-date="Mon, 30 Oct 2023 18:32:50 GMT"
Received: from DM4PR21MB3106.namprd21.prod.outlook.com (2603:10b6:8:62::18) by
DS7PR21MB3669.namprd21.prod.outlook.com with HTTPS; Thu, 26 Oct 2023 12:45:43
+0000
Received: from DM6PR00CA0022.namprd00.prod.outlook.com (2603:10b6:5:114::35)
by DM4PR21MB3106.namprd21.prod.outlook.com (2603:10b6:8:62::18) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6954.8; Thu, 26 Oct
2023 12:45:40 +0000
Received: from CY4PEPF0000FF2D.namprd00.prod.outlook.com
(2603:10b6:5:114:cafe::8b) by DM6PR00CA0022.outlook.office365.com
(2603:10b6:5:114::35) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6972.0 via Frontend
Transport; Thu, 26 Oct 2023 12:45:40 +0000
Authentication-Results: spf=pass (sender IP is 192.30.252.209)
smtp.mailfrom=github.com; dkim=pass (signature was verified)
header.d=github.com;dmarc=pass action=none
header.from=github.com;compauth=pass reason=100
Received-SPF: Pass (protection.outlook.com: domain of github.com designates
192.30.252.209 as permitted sender) receiver=protection.outlook.com;
client-ip=192.30.252.209; helo=out-26.smtp.github.com; pr=C
Received: from out-26.smtp.github.com (192.30.252.209) by
CY4PEPF0000FF2D.mail.protection.outlook.com (10.167.242.135) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6975.0 via Frontend Transport; Thu, 26 Oct 2023 12:45:40 +0000
Received: from github.com (hubbernetes-node-c0cb37e.ash1-iad.github.net [10.56.206.75])
by smtp.github.com (Postfix) with ESMTPA id 13627600C2A
for @.>; Thu, 26 Oct 2023 05:45:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2023; t=1698324340;
bh=2r8POlsW+e2oZDc8T284qGZmiJsLa28Axr20q7jTaZA=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=D3dk6xOQN3YrqDWqTEM1dQdYylXs71nIXLdV+/vx4TVM/fX5YouT27HvFmYZaske8
3RbyNJyPTukDPVQ3JL/AY0xRnI3OYXzuc6sETxzhbe1li8+CJAtfb7e6yV2i6dihW/
Dj8PkDApjet/L665cAnS9pdbSCvkPRjvnoyzr4O8=
Date: Thu, 26 Oct 2023 05:45:40 -0700
From: przlwo @.>
Reply-To: Azure/bicep-types-az @.>
To: Azure/bicep-types-az @.>
Cc: ccmaxpcrew @.>,
Mention @.>
Message-ID: @.>
In-Reply-To: @.>
References: @.>
Subject: Re: [Azure/bicep-types-az]
@. not idempotent (Issue #1441)
Content-Type: multipart/alternative;
boundary="--==_mimepart_653a5f7410bb07ad804321115";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: przlwo
X-GitHub-Recipient: ccmaxpcrew
X-GitHub-Reason: mention
List-ID: Azure/bicep-types-az
----==_mimepart_653a5f7410bb0_7ad804321115 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Hi, does the issue with Microsoft.CostManagement/views endpoint was resolved? Currently I'm facing this issue.
-- Reply to this email directly or view it on GitHub: https://github.com/Azure/bicep-types-az/issues/1441#issuecomment-1781051812 You are receiving this because you were mentioned.
Message ID: @.***> ----==_mimepart_653a5f7410bb0_7ad804321115 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Hi, does the issue with Microsoft.CostManagement/views endpoint was resolved? Currently I'm facing this issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
----==_mimepart_653a5f7410bb0_7ad804321115--
--_009DS7PR21MB366961B1AE3ACCC8002BDFF2DAA1ADS7PR21MB3669namp Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Mon, 30 Oct 2023 18:32:00 GMT"; modification-date="Mon, 30 Oct 2023 18:32:50 GMT"
Received: from MN0PR21MB3751.namprd21.prod.outlook.com (2603:10b6:208:3ca::10) by DS7PR21MB3669.namprd21.prod.outlook.com with HTTPS; Mon, 8 May 2023 18:19:33 +0000 Received: from DM6PR00CA0038.namprd00.prod.outlook.com (2603:10b6:5:331::7) by MN0PR21MB3751.namprd21.prod.outlook.com (2603:10b6:208:3ca::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6411.2; Mon, 8 May 2023 18:19:30 +0000 Received: from CB1PEPF00003D79.namprd00.prod.outlook.com (2603:10b6:5:331:cafe::53) by DM6PR00CA0038.outlook.office365.com (2603:10b6:5:331::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6405.0 via Frontend Transport; Mon, 8 May 2023 18:19:30 +0000 Authentication-Results: spf=pass (sender IP is 192.30.252.204) smtp.mailfrom=github.com; dkim=pass (signature was verified) he
Is there an update to this issue?
I can confirm, using...
resource costManagementView 'Microsoft.CostManagement/views@2023-11-01' ...
Still returns:
Status Message: Etag value required for update operation of view: test cost view. Please get the latest to avoid overwrite. (Request ID: <OBSCURED>) (Code:400)
I've written some modules to create action groups, create budgets (action group assigned), create the cost management views (with the same filter as the budget and the budget assigned as a KPI), and then a scheduled report of the view. I've got ~15-20 of these setup so it was ripe for building it in bicep.
My challenge with this bug - Since the Microsoft.CostManagement/views is not idempotent, I have to break the deployment into 3 components -
If I have to tweak the view, I have to delete the cost management view and then re-run #2 and #3 above. Since the view is deleted/re-created, users get an email anytime I have to do this causing confusion to the audience receiving the budget alerts (ex - "why am I getting so many messages that I've subscribed to the weekly report?!")
Side note - does anyone have a way to 'mass delete' cost management views? I was unable to find an azure powershell or cli command to do this so am manually purging them if needed.
Thanks!
Bicep version Bicep CLI version 0.4.1318 (ee0d808f35)
Describe the bug The API is not idempotent. You can create the resource the first time but when trying to reapply you get:
Status Message: Etag value required for update operation of report: test1.Please get the latest to avoid overwrite. (Request ID: 37dfcd1f-b755-45a0-bcd4-80eb27347b73) (Code:400)
if you try to add
at the same level as name you will get error:
To Reproduce Steps to reproduce the behavior:
Additional context Add any other context about the problem here.