Bevan Arps

Sorry, no. This component is display only, reliant on the markdown being externally supplied.

The NuGet package is unofficial; I reached out to the maintainer some time ago to see if I could publish an official one under the same name and haven't heard...

Thanks for the PR! I'll review this as soon as I get an opportunity.

Reopening as I intend to create an official package to replace the one kindly created by [fmuecke](https://www.nuget.org/profiles/fmuecke) so that they don't have the burden of maintenance.

_From the [Versioning](https://azure.github.io/azure-service-operator/design/versioning/#external-metadata-for-common-changes) spec:_ **External Metadata for common changes** We’ll capture common changes between versions in metadata (likely a YAML file) that we bundle with the code generator, allowing it...

Based on the current state of the generator, the solution should contain the following: When a property exists in one version of a resource, but not in the immediately following...

The changes commit [7a704f59](https://github.com/Azure/azure-resource-manager-schemas/commit/7a704f59e734099cef4a7fba901cca4fb0a5224d) are: ``` commit 7a704f59e734099cef4a7fba901cca4fb0a5224d Author: SDKAuto Date: Thu Jun 30 04:39:21 2022 +0000 CodeGen from PR 16919 in Azure/azure-rest-api-specs Exposing membershipType property from Access review APIs...

The generator error that revealed this problem was this: ``` E0705 11:19:21.793260 3454 gen_kustomize.go:111] Error during code generation: failed during pipeline stage 1/64: Load and walk schema: type filter action:...

Interestingly, as of commit [efb0537](https://github.com/Azure/azure-rest-api-specs/commit/efb0537b7f01b4f1d8c01685b7c0e76ae9baf5c6) in the [azure-rest-api-specs](https://github.com/Azure/azure-rest-api-specs) repo, the [2020-08-01-preview](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/authorization/resource-manager/Microsoft.Authorization/preview/2020-08-01-preview) API version is still present, so if/when we move to Swagger only, the immediate problem will be addressed.

This may be possible by adding `$azureGeneratedSecrets`. We'll add this to our backlog - given it's a simple change, we'd also accept a PR.