Municipal IaC apply fails because a parameter still points at a retired provider API version that the control plane no longer accepts. What is the best characterization of the failure?
Select an answer to reveal the explanation.
Short Explanation
That parameter still names an API version the provider wheeled to the curb. Update the IaC to a supported API and re-apply. Deprecation breaks deploys until the template catches up—no mystery DNS required.
Full Explanation
Provider API deprecation invalidates templates that still pin retired versions, causing apply failures until configurations are upgraded. Transient DNS theories or assumptions of indefinite support do not restore a retired control-plane API. Cloud+ Domain 6.1 includes deprecation-driven deployment breakage among issues operators must troubleshoot.