Upgrade notes
Breaking: the fqdn output is now unknown until apply.
Hostnames previously came from string concatenation with a hardcoded core.windows.net, so sovereign clouds got names that do not resolve. An account in Azure US Government reported mysa.blob.core.windows.net while Azure had provisioned mysa.blob.core.usgovcloudapi.net.
The output now reads properties.primaryEndpoints from the account, so it carries the correct DNS suffix for the target cloud. Because the value comes from an API response, it is no longer known at plan time.
Action required only if you use fqdn in a for_each, count, or provider argument. Move that value to a static input or use -target on the first apply. The shape is unchanged: hostnames without scheme or trailing slash, keyed by declared sub-resources.
Also in this release
private_endpointsnow matches the AVM interface. Three optional attributes were added:role_assignments.name,lock.notes, andip_configurations.member_name.subresource_nameis typed optional, with a validation rule that keeps it required.- Containers and the static website submodule now apply after the blob service. Both wrote
blobServices/defaultconcurrently, and the later write dropped the earlier one's fields. immutable_storage_with_versioningcannot be combined withblob_properties.restore_policy. This is now documented.
What's Changed
Bug Fixes
- fix: derive fqdn suffix from returned storage endpoints by @myaschmitz in #399
Other Changes
- fix: order containers after blob service (#392) by @myaschmitz in #395
- fix: order static website after blob service by @myaschmitz in #397
Full Changelog: v0.9.0...v0.10.0