Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/content/usage/pipeline-automation/_index.md
Original file line number Diff line number Diff line change
@@ -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
6 changes: 6 additions & 0 deletions docs/content/usage/pipeline-automation/bicep.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
draft: false
title: Bicep - Pipeline Automation
linktitle: Bicep
description: Bicep Pipeline Automation for the Azure Verified Modules (AVM) program
---
6 changes: 6 additions & 0 deletions docs/content/usage/pipeline-automation/terraform.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
draft: false
title: Terraform - Pipeline Automation
linktitle: Terraform
description: Terraform Pipeline Automation for the Azure Verified Modules (AVM) program
---
11 changes: 1 addition & 10 deletions docs/content/usage/sol-dev.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
24 changes: 24 additions & 0 deletions docs/hugo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -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'
Expand Down