Microsoft.Insights/components - retentionInDays incorrectly marked readonly

[anthony-c-martin]

Originally reported under Azure/bicep#3212. On testing, the service actually allows this value to be modified via a PUT.

See

azure-rest-api-specs/specification/applicationinsights/resource-manager/Microsoft.Insights/preview/2020-02-02-preview/components_API.json

Lines 552 to 556 in b5f8384

	"RetentionInDays": {
	"type": "integer",
	"description": "Retention period in days.",
	"readOnly": true
	},

This may also affect other apiVersions.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azmonapplicationinsights.

Issue Details

---

Originally reported under Azure/bicep#3212. On testing, the service actually allows this value to be modified via a PUT.

See

azure-rest-api-specs/specification/applicationinsights/resource-manager/Microsoft.Insights/preview/2020-02-02-preview/components_API.json

Lines 552 to 556 in b5f8384

	"RetentionInDays": {
	"type": "integer",
	"description": "Retention period in days.",
	"readOnly": true
	},

This may also affect other apiVersions.

Author:	anthony-c-martin
Assignees:	leni-msft
Labels:	Monitor - ApplicationInsights, Service Attention, needs-triage
Milestone:	-

[timja]

This is blocking the azurerm terraform provider adoption of the workspace model with application insights

[leniatgh]

@zakimaksyutov @igorse would you be able to take a look at this issue or route to correct person? Thanks!

[dylanmorley]

Fixed by #15247

[Jaroslaw-Roman-Cudzich]

Hello,

Thank you for the fix.

For testing purposes, please keep in mind that as per https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-retention-archive?tabs=portal-1%2Cportal-2 , a change in the RetentionInDays value can only be tested after 30 days time after the change as "Azure Monitor waits 30 days before removing the data, so you can revert the change and prevent data loss in the event of an error in configuration."