From 5b82af712b0f41bd90d49d8265d9896ceda885b7 Mon Sep 17 00:00:00 2001 From: Mate Barabas Date: Mon, 2 Jun 2025 08:34:18 -0700 Subject: [PATCH 1/2] scaffolding for pipeline automation --- .../usage/pipeline-automation/_index.md | 9 +++++++ .../usage/pipeline-automation/bicep.md | 6 +++++ .../usage/pipeline-automation/terraform.md | 6 +++++ docs/hugo.toml | 24 +++++++++++++++++++ 4 files changed, 45 insertions(+) create mode 100644 docs/content/usage/pipeline-automation/_index.md create mode 100644 docs/content/usage/pipeline-automation/bicep.md create mode 100644 docs/content/usage/pipeline-automation/terraform.md diff --git a/docs/content/usage/pipeline-automation/_index.md b/docs/content/usage/pipeline-automation/_index.md new file mode 100644 index 000000000..52d75e4f8 --- /dev/null +++ b/docs/content/usage/pipeline-automation/_index.md @@ -0,0 +1,9 @@ +--- +title: Piepline Automation +linktitle: Piepline Automation +type: default +weight: 3 +description: Pipeline Automation for the Azure Verified Modules (AVM) program +--- + +## Blah diff --git a/docs/content/usage/pipeline-automation/bicep.md b/docs/content/usage/pipeline-automation/bicep.md new file mode 100644 index 000000000..0508dc948 --- /dev/null +++ b/docs/content/usage/pipeline-automation/bicep.md @@ -0,0 +1,6 @@ +--- +draft: false +title: Bicep - Pipeline Automation +linktitle: Bicep +description: Bicep Pipeline Automation for the Azure Verified Modules (AVM) program +--- diff --git a/docs/content/usage/pipeline-automation/terraform.md b/docs/content/usage/pipeline-automation/terraform.md new file mode 100644 index 000000000..fadc6426a --- /dev/null +++ b/docs/content/usage/pipeline-automation/terraform.md @@ -0,0 +1,6 @@ +--- +draft: false +title: Terraform - Pipeline Automation +linktitle: Terraform +description: Terraform Pipeline Automation for the Azure Verified Modules (AVM) program +--- diff --git a/docs/hugo.toml b/docs/hugo.toml index 7a5d1bce2..49e2d765f 100644 --- a/docs/hugo.toml +++ b/docs/hugo.toml @@ -126,6 +126,30 @@ params = { alwaysopen = true, collapsibleMenu = true } weight = 2 params = { alwaysopen = false, collapsibleMenu = true } + [[menu.defined]] + identifier = 'pipeline-automation' + parent = 'usage' + name = 'Pipeline Automation' + pageRef = '/usage/pipeline-automation' + weight = 3 + params = { alwaysopen = false, collapsibleMenu = true } + + [[menu.defined]] + identifier = 'bicep-pipeline-automation' + parent = 'pipeline-automation' + name = 'Bicep' + pageRef = '/usage/pipeline-automation/bicep' + weight = 1 + params = { alwaysopen = false, collapsibleMenu = true } + + [[menu.defined]] + identifier = 'terraform-pipeline-automation' + parent = 'pipeline-automation' + name = 'Terraform' + pageRef = '/usage/pipeline-automation/terraform' + weight = 2 + params = { alwaysopen = false, collapsibleMenu = true } + # [[menu.defined]] # identifier = 'concepts' # parent = 'usage' From 37afbe2f8369361504182235342fb043939ff269 Mon Sep 17 00:00:00 2001 From: Mate Barabas Date: Mon, 2 Jun 2025 12:25:02 -0700 Subject: [PATCH 2/2] removing points that have been covered in the previous release --- docs/content/usage/sol-dev.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/docs/content/usage/sol-dev.md b/docs/content/usage/sol-dev.md index 0c8bde157..b59234c73 100644 --- a/docs/content/usage/sol-dev.md +++ b/docs/content/usage/sol-dev.md @@ -6,17 +6,8 @@ weight: 4 description: Advanced Solution Development guidance for the Azure Verified Modules (AVM) program. It covers the technical decisions and concepts that are important for building and deploying Azure solutions using AVM modules. --- -## Considerations and steps of Solution Development +## Questions to cover -- Decide on the IaC language (Bicep or Terraform) -- Decide on the module sourcing method (public registry, private registry, inner-sourcing) -- Decide on the orchestration method (template or pipeline) -- Identify the resources needed for the solution (are they all available in AVM?) -- Implement, validate, deploy, test the solution - -## Questions to cover on this page - -- Pick a realistically complex solution and demonstrate how to build it using AVM modules - Best practices for coding (link to official language specific guidance AND AVM specs where/if applicable) - Best practices for input and output parameters