From 22e5cb347f1eb2ad2c2af05cf42dd8f5cc16c321 Mon Sep 17 00:00:00 2001 From: Stagge Date: Thu, 18 Sep 2025 12:54:56 +0200 Subject: [PATCH 1/3] Add README --- contributions/demo/jsoderho-jstagge/README.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 contributions/demo/jsoderho-jstagge/README.md diff --git a/contributions/demo/jsoderho-jstagge/README.md b/contributions/demo/jsoderho-jstagge/README.md new file mode 100644 index 000000000..4bee8169d --- /dev/null +++ b/contributions/demo/jsoderho-jstagge/README.md @@ -0,0 +1,28 @@ +# Assignment Proposal + +## Title + +Reusable Infrastructure with Bicep Modules + +## Names and KTH ID + +- John Söderholm (jsoderho@kth.se) +- Jonatan Stagge (jstagge@kth.se) + +## Deadline + +- Week 5 + +## Category + +- Demo + +## Description + +This demonstration will showcase Bicep Modules for creating reusable, consistent, and scalable Azure infrastructure components. We will illustrate how common infrastructure patterns, such as a secure web server, can be defined once as a Bicep module and then deployed multiple times with different configurations, eliminating code duplication and promoting standardisation. + +We will begin by outlining the challenges of managing Azure infrastructure without reusable code and introduce Bicep Modules as the solution. Next, we will quickly show a pre-built Bicep module that defines a standard web server (an Azure Virtual Machine with Nginx and the necessary networking resources), and then use it to deploy an initial web server to Azure. For the core of the demo, we will add additional web servers by simply reusing the same module with different settings, showcasing the clear benefits of this reusable approach. + +**Relevance** + +By showcasing reusable Bicep modules, we illustrate how organisations can accelerate deployment cycles, ensure standardised and reliable environments across all stages, and significantly reduce operational overhead. This approach minimises configuration drift, improves maintainability, and enables development teams to provision Azure resources rapidly, thereby streamlining the entire software delivery pipeline. From fb53da5493eb17936a804e8a5064efd76edccfba Mon Sep 17 00:00:00 2001 From: Stagge Date: Thu, 18 Sep 2025 12:58:43 +0200 Subject: [PATCH 2/3] Move directory --- contributions/demo/{ => week5}/jsoderho-jstagge/README.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename contributions/demo/{ => week5}/jsoderho-jstagge/README.md (100%) diff --git a/contributions/demo/jsoderho-jstagge/README.md b/contributions/demo/week5/jsoderho-jstagge/README.md similarity index 100% rename from contributions/demo/jsoderho-jstagge/README.md rename to contributions/demo/week5/jsoderho-jstagge/README.md From 2dab0f8fd9cd75fdafc503a3527c09813626568f Mon Sep 17 00:00:00 2001 From: Stagge Date: Wed, 8 Oct 2025 15:40:31 +0200 Subject: [PATCH 3/3] Add deliverables --- .../executable-tutorial/roboam-jstagge/README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/contributions/executable-tutorial/roboam-jstagge/README.md b/contributions/executable-tutorial/roboam-jstagge/README.md index 849954e07..3bb5ac006 100644 --- a/contributions/executable-tutorial/roboam-jstagge/README.md +++ b/contributions/executable-tutorial/roboam-jstagge/README.md @@ -30,4 +30,10 @@ The tutorial will use practical examples with repositories containing simulated **Relevance** -Secret sprawl is one of the most common security risks in DevSecOps. Tools like Gitleaks helps to prevent credentials from ever reaching version control. This knowledge is highly relevant for DevOps engineers, since mismanaged secrets can lead to major security breaches and compliance issues, even on private repositories. \ No newline at end of file +Secret sprawl is one of the most common security risks in DevSecOps. Tools like Gitleaks helps to prevent credentials from ever reaching version control. This knowledge is highly relevant for DevOps engineers, since mismanaged secrets can lead to major security breaches and compliance issues, even on private repositories. + +**Deliverables** + +Tutorial: https://killercoda.com/stagge/scenario/gitleaks-tutorial + +Repository: https://github.com/Stagge/gitleaks-tutorial \ No newline at end of file