This updates the CMS dependency to 11.0.0-rc6 and includes manually created JSON schemas.
The JSON schemas couldn't be automatically generated using a CLI tool because of a circular dependency: the tool needed a reference to the projects containing the CdnMediaUrlProviderOptions and AzureBlobFileSystemOptions classes, but those projects invoked the CLI to generate the schema during build.
The AzureBob section can also contain a 'special' Media property or arbitrary names, which have a slight difference in required properties (as we automatically set the VirtualPath for media based on the UmbracoMediaPath setting). This required some manual tweaking of the JSON schema to accomplish.
Testing can be done by adding the build artifacts as package references to an empty CMS 11.0.0-rc6 site and checking whether the JSON schemas (appsettings-schema.Umbraco.StorageProviders.json and appsettings-schema.Umbraco.StorageProviders.AzureBlob.json) are copied over, references are added to the appsettings-schema.json file and auto-completion/validation in your IDE works as expected (you might need to re-open the project to force the IDE to refresh the schema). You can optionally also setup Azure Blob Storage and test whether that still works as expected, although there hasn't been any code changes in this project since the last RC release.
This updates the CMS dependency to 11.0.0-rc6 and includes manually created JSON schemas.
The JSON schemas couldn't be automatically generated using a CLI tool because of a circular dependency: the tool needed a reference to the projects containing the
CdnMediaUrlProviderOptions
andAzureBlobFileSystemOptions
classes, but those projects invoked the CLI to generate the schema during build.The
AzureBob
section can also contain a 'special' Media property or arbitrary names, which have a slight difference in required properties (as we automatically set theVirtualPath
for media based on theUmbracoMediaPath
setting). This required some manual tweaking of the JSON schema to accomplish.Testing can be done by adding the build artifacts as package references to an empty CMS 11.0.0-rc6 site and checking whether the JSON schemas (
appsettings-schema.Umbraco.StorageProviders.json
andappsettings-schema.Umbraco.StorageProviders.AzureBlob.json
) are copied over, references are added to theappsettings-schema.json
file and auto-completion/validation in your IDE works as expected (you might need to re-open the project to force the IDE to refresh the schema). You can optionally also setup Azure Blob Storage and test whether that still works as expected, although there hasn't been any code changes in this project since the last RC release.