Tim Lovell-Smith

> }, As well as an initial 202 response code, you need a final successful response status. --- Refers to: specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2023-08-01/service.json:956 in 01e549d. [](commit_id = 01e549dba97f55cae8948d8ec0459b35304c20fd, deletion_comment = False)

> > > > > ``` > > > > > "post": { > > > > > ``` > > > > > > > > > > >...

Please could you complete due diligence checklist, and confirm that this is a proposal to add a new property in the response to an existing shipped API version that could...

> "entraIdPrincipal": { I think we shouldn't put the brand 'entra' in the API if we can think of a good alternative. Rebranding will make the API naming age ungracefully......

> }, Please note that booleans are hard to extend and not future proof, so discouraged. Consider using an enum or other optional property instead. --- Refers to: specification/postgresqlhsc/resource-manager/Microsoft.DBforPostgreSQL/preview/2023-03-02-preview/postgresqlhsc.json:2610 in...

> "password": { Great to see it won't be required! How will someone know whether it was ever set or not though? Since you can't see a password set in...

Technically we could also have a validation regex for allowed values, but that's something that depends on the redis version, which will be hard to model and keep up to...

@dw511214992 My thinking is that because its customer reported bugfix to the swagger for this api-version, it can't be in a new api-version.

Sory for the lack of progress. I think we're all happy with this as a bugfix to docs from an ARM perspective, its just breaking change / versioning analysis needed.

@JeffreyRichter Do you think this contribution is okay as is, as a breaking change bugfix?