Skip to content

Commit

Permalink
Cms/calinator444/ssw.rules.content/rule/azure resources creating/rule (
Browse files Browse the repository at this point in the history
…SSWConsulting#8604)

* Update Rule “azure-resources-creating/rule”

* Update Rule “azure-resources-creating/rule”

* Update Rule “azure-resources-creating/rule”

* Update Rule “azure-resources-creating/rule”

* Update rules/azure-resources-creating/rule.md

My bad, thanks for cleaning that up :)

Co-authored-by: William Liebenberg [SSW • Microsoft MVP] <[email protected]>

---------

Co-authored-by: William Liebenberg [SSW • Microsoft MVP] <[email protected]>
  • Loading branch information
Calinator444 and william-liebenberg authored May 28, 2024
1 parent 0e1690e commit 1e64462
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions rules/azure-resources-creating/rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,13 @@ created: 2020-10-06T00:13:27.000Z
archivedreason: null
guid: 007dd1f6-8ac6-4840-8f4f-a39c6f847880
---

We've been down this road before where developers had to be taught not to manually create databases and tables. Now, in the cloud world, we're saying the same thing again: **Don't manually create Azure resources.**

<!--endintro-->

### Manually Creating Resources

This is the most common and the worst. This is bad because it requires manual effort to reproduce and leaves margin for human error.
This is the most common and the worst. This is bad because it requires manual effort to reproduce and leaves margin for human error. Manually provisioning resources can also lead to [configuration drift](https://learn.microsoft.com/en-us/devops/deliver/what-is-infrastructure-as-code#avoid-manual-configuration-to-enforce-consistency), which is to say that over time it can be difficult to keep track of which deployment configurations were made and why.

* Create resources in Azure and not save a script

Expand Down Expand Up @@ -76,6 +75,7 @@ So if you aren't manually creating your Azure resources, what options do you hav
* Has ['az' command line integration](https://docs.microsoft.com/en-us/cli/azure/bicep?view=azure-cli-latest)
* Awesome [extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep) for VS Code to author ARM Bicep files ⭐️
* Under the covers - Compiles into an ARM JSON template for deployment
* Improves the repeatability of your deployment process, which can come in handy when you want to stage your deployment configuration
* Much simpler syntax than ARM JSON
* Handles resource dependencies automatically
* [Private Module Registries](https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/private-module-registry?tabs=azure-powershell) for publishing versioned and reusable architectures
Expand Down

0 comments on commit 1e64462

Please sign in to comment.