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
The scripts are currently imperative instead of declarative (difference explained). Imperative scripts are more prone to break because they deal the "how" when creating resources. The "how" may change when Azure makes changes to resources or dependencies.
By using declarative syntax you can focus on the "what" instead of the "how", you let Azure handle the "how". Because of this Azure can change the underlying way of creating resources without impacting the final created resources.
By refactoring imperative scripts to declarative files this project becomes easier to maintain by being more resistent to breaking Azure changes.
Azure resources like the AKS cluster are currently create using imperative scripts:
The scripts are currently imperative instead of declarative (difference explained). Imperative scripts are more prone to break because they deal the "how" when creating resources. The "how" may change when Azure makes changes to resources or dependencies.
By using declarative syntax you can focus on the "what" instead of the "how", you let Azure handle the "how". Because of this Azure can change the underlying way of creating resources without impacting the final created resources.
By refactoring imperative scripts to declarative files this project becomes easier to maintain by being more resistent to breaking Azure changes.
Resources:
The text was updated successfully, but these errors were encountered: