Azure / Azure/bicep-types-az

[Microsoft.DBforMySQL/flexibleServers/configurations]: `properties` shouldn't be marked as read-only?

Open
#1,386 1 comment 0 reactions 0 assignees View on GitHub
inaccuracy No RP Github RP: Microsoft.DBforMySQL
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

### Resource Type

Microsoft.DBforMySQL/flexibleServers/configurations

### Api Version

2021-05-01

### Issue Type

Property(s) inaccurately marked read-only/write-only

### Other Notes

The following warnings are generated by the Bicep linter:

`Warning BCP245: Resource type "Microsoft.DBforMySQL/flexibleServers/configurations@2021-05-01" can only be used with the 'existing' keyword.`

`Warning BCP073: The property "properties" is read-only. Expressions cannot be assigned to read-only properties.`

However, I am able to declare the type in question as a regular resource and successfully update MySQL Flexible Server parameters through it.

### Bicep Repro

_No response_

### Confirm

- [X] I have searched this repository and have not found similar issue reports.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Microsoft.DBforMySQL/flexibleServers/configurations resource type at API version 2021-05-01 and inspect why `properties` is marked read-only. Verify the behavior against the reported Bicep linter warnings and the ability to update MySQL Flexible Server parameters; done means a regular resource declaration accepts the update without those warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.