You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when host is aks, azd will do an auto-post-provision hook to do aks deployments or config.
Since phase 1 doesn't have aks provisioned, then this will fail with:
ERROR: deployment failed: failed invoking event handlers for 'postprovision', failed retrieving cluster admin credentials. Ensure your cluster has been configured to support admin credentials, parameter resourceName cannot be empty
I would like the post-provision hook to fail gracefully if the aks resources don't exist.
The text was updated successfully, but these errors were encountered:
@wbreza can you take a look? Is this related some of the asks we had around provisioning with specific bicep files/resources or a service-level provisioning?
This partially aligns with some of the proposed for the new AI/ML apps support in azd.
Move target resource discovery to service targets
Right now target resource discovery occurs globally within azd. Some service targets support delayed provisioning and we currently have a less than ideal implementation.
Moving to target resource discovery to each service target will give additional flexibility for resource discovery and offer an improve implementation.
After this work is done we can also introduce standardized warnings/errors where a missing resource can be bubbled up correctly to the UX noting the deployment is skipped due to missing resource but continue with remaining services without throwing a fatal error.
I have a two phase provision:
phase 1
phase 2:
when host is aks, azd will do an auto-post-provision hook to do aks deployments or config.
Since phase 1 doesn't have aks provisioned, then this will fail with:
I would like the post-provision hook to fail gracefully if the aks resources don't exist.
The text was updated successfully, but these errors were encountered: