From f8ee275312d1b0d5847a56b7377cc2487f519495 Mon Sep 17 00:00:00 2001 From: Johannes Scheuerer Date: Tue, 15 Oct 2024 10:16:01 +0200 Subject: [PATCH] Delete docs/lab2.md --- docs/lab2.md | 79 ---------------------------------------------------- 1 file changed, 79 deletions(-) delete mode 100644 docs/lab2.md diff --git a/docs/lab2.md b/docs/lab2.md deleted file mode 100644 index cfe2e7d..0000000 --- a/docs/lab2.md +++ /dev/null @@ -1,79 +0,0 @@ -# Usecase 2 - Templates and NoCode - -## Overview - What's in the section? -Time: ~30 minutes - -In this section, we will begin to make use of the StackGuardian marketplace, which can be seen as a library for templates and blueprints. But it is more than that - it also allows you to manage the version and lifecycle of your IaC templates, across different protocols (like Terraform, Ansible Playbooks, Helm Charts etc..), combine multiple templates/protocols into a stack and use NoCode to deploy them. -The goal of this use-case is to demonstrate the following: - -* Standardize on blueprints and templates -* Collaborate between teams in an organisation -* NoCode Interface to simplify deployment of infrastructure -* Versioning and lifecycle of templates - - -![Usecase 2](image/usecase2.png) -_Fig. Use the marketplace to manage and deploy templates_ - -## 2.1 - Create an IaC template -### Description -In this lab you will see how quickly a new template in the library can be created. - - -### Create an IaC template -In the orchestrator on the left click on **Library** and choose **Create Template +**. - - -![Create Template](image/createtemplate.png) -_Fig. Create IaC template_ - -1. Template Name = ``vpc-xx`` -2. Scroll down and set Source Config Kind = **TERRAFORM** -3. Source Destination Kind = **github.com** -4. Repository URL = ``https://github.com/StackGuardian/terraform-aws-vpc`` -5. On the bottom right of the screen click **Generate No Code Form** -6. By scrolling down you see the variables that were identified in the IaC and loaded into the template. -7. Hit **Create** to add this template to your marketplace. - -The creation process will bring you directly into the marketplace interface. Here you can explore the tabs Usage, Analysis, Code, Meta now. -Later on the instructor will go through the different tabs with the whole group - -If you want to move back to the **orchestrator** go to the left top corner and click on the **9dots**. - - -## 2.2 - Deploy an AWS VPC from existing template via NoCode -### Description -In this exercise you will **NOT** use the previously created template. -Rather we put you in the shoes of a Cloud Consumer or Developer, who is not too much into IaC syntax. The NoCode interfaces allows also non-IaC-experts to use IaC. - -### Deploy infrastructure from template -Change back into the orchestrator and click on **Workflow Groups** in the menubar. - -1. Choose your workflow group **wfg-xx**. -2. On the right top you can find **Create Workflow >> Use Wizard >> Terraform** -3. Source Type = **Subscribed Templates** -4. Browse Templates = ``vpc`` -5. Choose **terraform-aws-vpc-stripped** and under template revision the latest revision. -6. The form below should have the following entries - * VPC Name = ``marketplace-vpc-xx`` - * Region with Availabilty Zones = ``Frankfurt`` - * CIDR Block for VPC = _choose one_ - * Public Subnets IP Addresses = _choose one_ - * Private Subnets IP Addresses = _choose one_ -7. Click **Next** ---- - -8. Under Deployment Environment select the connector = **AWS-Deploy-Role** -9. **Next** ---- -10. Workflow Name = ``marketplace-vpc-xx`` (this is the name for the resource in the StackGuardian interface) -11. **Next** ---- -12. Review the configuration and click **Launch** ---- -13. To run the workflow choose the **Terraform Action: Create** and click **Quick Run** ---- - -In the **Runs** tab you can now follow the deployment. Once the VPC is ready, the Status will change to **Completed**. - -The instructor will show the different capabilities in the marketplace. If you have a usecase in mind, feel free to ask how this can be done in StackGuardian.