IaC folder done

remotesynth · remotesynth · commit 3e4e2bc40cfe · 2025-06-19T09:56:42.000-04:00
diff --git a/src/content/docs/aws/integrations/infrastructure-as-code/cloud-custodian.md b/src/content/docs/aws/integrations/infrastructure-as-code/cloud-custodian.md
diff --git a/src/content/docs/aws/integrations/infrastructure-as-code/crossplane.md b/src/content/docs/aws/integrations/infrastructure-as-code/crossplane.md
@@ -39,19 +39,23 @@ The installation may take a few minutes.
 In parallel, we can install the `crossplane` command-line tool.
 ```bash
 curl -sL https://raw.githubusercontent.com/crossplane/crossplane/master/install.sh | bash
-{/* <disable-copy>...</disable-copy> */} {/* mdx-disabled */}
 sudo mv crossplane /usr/local/bin
 ```
 To confirm that the installation was successful, we can run these commands, which should yield output similar to the following:
 ```bash
 crossplane version
-{/* <disable-copy>Client Version: v1.17.0 */} {/* mdx-disabled */}
-Server Version: v1.17.0</disable-copy>
+```
+```bash title="Output"
+Client Version: v1.17.0
+Server Version: v1.17.0
+```
 
+```bash
 kubectl get crds | grep crossplane
-{/* <disable-copy>compositions.apiextensions.crossplane.io                     2023-09-03T11:30:36Z */} {/* mdx-disabled */}
+```
+```bash title="Output"
+compositions.apiextensions.crossplane.io                     2023-09-03T11:30:36Z
 configurations.pkg.crossplane.io                             2023-09-03T11:30:36Z
-...</disable-copy>
 ```
 
 ### Installing the Crossplane AWS Provider
@@ -87,12 +91,13 @@ EOF
 
 After some time, the providers should get into healthy state, which can be confirmed via `kubectl get providers`:
 ```bash
-{/* kubectl get providers<disable-copy> */} {/* mdx-disabled */}
+kubectl get providers
+```
+```bash title="Output"
 NAME                          INSTALLED   HEALTHY   PACKAGE                                               AGE
 upbound-provider-family-aws   True        True      xpkg.upbound.io/upbound/provider-family-aws:v0.40.0   2m
 provider-aws-s3               True        True      xpkg.upbound.io/upbound/provider-aws-s3:v0.40.0       2m
 provider-aws-sqs              True        True      xpkg.upbound.io/upbound/provider-aws-sqs:v0.40.0      2m
-</disable-copy>
 ```
 
 Next, we install a secret to define the test credentials for the AWS provider:
@@ -139,12 +144,10 @@ EOF
 ```
 
 :::note
-
 The endpoint `http://host.docker.internal:4566` in the listing above assumes that you are running Kubernetes in the local Docker engine, and that LocalStack is up and running and available on default port `4566`.
 :::
 
 :::note
-
 The Crossplane AWS provider currently requires us to specify the list of `services` for which the local `endpoint` is used as the target URL.
 Please make sure to extend this list accordingly if you're working with additional LocalStack services.
 :::
@@ -169,18 +172,20 @@ EOF
 If everything is wired up correctly, you should now see some activity in the LocalStack log outputs, where Crossplane starts deploying the S3 bucket against LocalStack.
 After some time, the bucket should be transitioning into `ready` state within Crossplane:
 ```bash
-{/* kubectl get buckets<disable-copy> */} {/* mdx-disabled */}
+kubectl get buckets
+```
+```bash
 NAME                     READY   SYNCED   EXTERNAL-NAME            AGE
 crossplane-test-bucket   True    True     crossplane-test-bucket   30s
-</disable-copy>
 ```
 
 ...
 and the bucket it should also be visible when querying the local S3 buckets in LocalStack via [`awslocal`](https://github.com/localstack/awscli-local):
 ```bash
-{/* awslocal s3 ls<disable-copy> */} {/* mdx-disabled */}
+awslocal s3 ls
+```
+```bash title="Output"
 2023-09-03 15:18:47 crossplane-test-bucket
-</disable-copy>
 ```
 
 We can repeat the same exercise for creating a local SQS queue named `crossplane-test-queue`:
@@ -199,22 +204,24 @@ EOF
 
 After some time, the queue should transition into `ready` state in Crossplane:
 ```bash
-{/* kubectl get queues<disable-copy> */} {/* mdx-disabled */}
+kubectl get queues
+```
+```bash title="Output"
 NAME                    READY   SYNCED   EXTERNAL-NAME                                                         AGE
 crossplane-test-queue   True    True     http://host.docker.internal:4566/000000000000/crossplane-test-queue   40s
-</disable-copy>
 ```
 
-...
-and the queue should be visible when listing the SQS queues in LocalStack:
+...and the queue should be visible when listing the SQS queues in LocalStack:
 ```bash
-{/* awslocal sqs list-queues<disable-copy> */} {/* mdx-disabled */}
+awslocal sqs list-queues
+```
+
+```bash title="Output"
 {
     "QueueUrls": [
         "http://localhost:4566/000000000000/crossplane-test-queue"
     ]
 }
-</disable-copy>
 ```
 
 ### Summary
diff --git a/src/content/docs/aws/integrations/infrastructure-as-code/former2.md b/src/content/docs/aws/integrations/infrastructure-as-code/former2.md
@@ -66,33 +66,45 @@ You can verify that the resources were created successfully by running the follo
 
 ```bash
 localstack logs
-{/* <disable-copy> */} {/* mdx-disabled */}
+```
+
+```bash title="Output"
 2023-10-14T15:31:08.852  INFO --- [   asgi_gw_0] localstack.request.aws     : AWS s3.CreateBucket => 200
 2023-10-14T15:31:09.356  INFO --- [   asgi_gw_0] localstack.request.aws     : AWS sqs.CreateQueue => 200
 2023-10-14T15:31:12.920  INFO --- [   asgi_gw_0] botocore.credentials       : Found credentials in environment variables.
 2023-10-14T15:31:13.332  INFO --- [   asgi_gw_0] localstack.utils.bootstrap : Execution of "require" took 2028.25ms
 2023-10-14T15:31:13.712  INFO --- [   asgi_gw_0] localstack.request.aws     : AWS dynamodb.CreateTable => 200
-</disable-copy>
+```
+
+```bash
 awslocal s3 ls
-<disable-copy>
+```
+```bash title="Output"
 2023-10-14 21:01:08 my-bucket
-</disable-copy>
+```
+
+```bash
 awslocal sqs list-queues
-<disable-copy>
+```
+
+```bash title="Output"
 {
     "QueueUrls": [
         "http://localhost:4566/000000000000/my-queue"
     ]
 }
-</disable-copy>
+```
+
+```bash
 awslocal dynamodb list-tables
-<disable-copy>
+```
+
+```bash title="Output"
 {
     "TableNames": [
         "my-table"
     ]
 }
-</disable-copy>
 ```
 
 ### Configure Former2
@@ -102,15 +114,13 @@ Open the [**Credentials**](https://former2.com/#section-setup-credentials) tab a
 For LocalStack, you can just configure the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables as `test` and `test`, respectively.
 
 ![Enter test credentials on Former2 Dashboard](/images/aws/former2-credentials.png)
-<br></br>
 
 Click on [**Continue to Parameters**](https://former2.com/#section-setup-parameters) and include your own CloudFormation stack parameters by adding them below.
 Click on [**Continue to Settings**](https://former2.com/#section-setup-settings) and navigate to **Custom Endpoints**.
 Toggle the **Use LocalStack Endpoint** switch to enable the LocalStack endpoint URL (`http://localhost:4566`).
 Click on [**Go to Dashboard**](https://former2.com/#section-dashboard) to complete the setup.
 
 ![LocalStack endpoint toggle on Former2 Dashboard](/images/aws/former2-localstack-endpoint.png)
-<br></br>
 
 You can now click on **Scan Account** button on the top-right corner of the dashboard to scan your LocalStack instance for resources.
 Once the scan is complete, you can select the resources you want to generate IaC outputs for.
@@ -120,12 +130,10 @@ Once the scan is complete, you can select the resources you want to generate IaC
 Navigate to [S3](https://former2.com/#section-storage-s3), [DynamoDB](https://former2.com/#section-database-dynamodb), and [SQS](https://former2.com/#section-applicationintegration-sqs) to verify that the resources you created earlier are listed.
 
 ![S3 Console on Former2 Dashboard](/images/aws/former2-s3.png)
-<br></br>
 
 You can select the resources you want to generate IaC outputs for and click on **Add Selected**.
 Finally, you can click on **Generate** on the top-left corner of the dashboard to generate the IaC outputs.
 
 ![CloudFormation Output on Former2 Dashboard](/images/aws/former2-cloudformation-output.png)
-<br></br>
 
 You can also choose to generate the IaC outputs in a different format by clicking on the various options available on the left-hand side of the dashboard.
diff --git a/src/content/docs/aws/integrations/infrastructure-as-code/pulumi.mdx b/src/content/docs/aws/integrations/infrastructure-as-code/pulumi.mdx
@@ -6,6 +6,8 @@ sidebar:
     order: 2
 ---
 
+import { FileTree } from "@astrojs/starlight/components";
+
 ## Introduction
 
 Pulumi's SDK for infrastructure-as-code allows you to create, deploy, and manage AWS containers, serverless functions, and other infrastructure using popular programming languages.
@@ -22,7 +24,6 @@ This guide will show you how to set up local AWS resources using both the `pulum
 ## `pulumilocal` wrapper script
 
 :::note
-
 `pulumi-local` currently does not support the `aws-native` package as it relies on the AWS Cloud Control API.
 For additional information, refer to the [GitHub issue](https://github.com/localstack/localstack/issues/11523).
 :::
@@ -43,7 +44,6 @@ export PULUMI_BACKEND_URL=file://`pwd`/myproj
 ```
 
 :::note
-
 For further options please consult the official documentation on available  [environment variables](https://www.pulumi.com/docs/cli/environment-variables/) and [local backend](https://www.pulumi.com/docs/concepts/state/#local-filesystem).
 :::
 
@@ -59,10 +59,10 @@ You can now use the `pulumilocal` command to interact with your Pulumi project.
 
 ```bash
 pulumilocal --help
-{/* <disable-copy> */} {/* mdx-disabled */}
+```
+```bash title="Output"
 Pulumi - Modern Infrastructure as Code
 ...
-<disable-copy>
 ```
 
 ### Create a new Pulumi project
@@ -75,7 +75,6 @@ pulumilocal new aws-typescript -y -s lsdev --cwd myproj
 ```
 
 :::tip
-
 The `--cwd` option is unnecessary if you're already in the project directory.
 :::
 
@@ -142,24 +141,22 @@ Installing dependencies...
 
 This will create the following directory structure.
 
-```bash
-tree -L 1
-.
-├── index.ts
-├── node_modules
-├── package.json
-├── package-lock.json
-├── Pulumi.dev.yaml
-├── Pulumi.yaml
-└── tsconfig.json
-```
+<FileTree>
+- index.ts
+- node_modules
+- package.json
+- package-lock.json
+- Pulumi.dev.yaml
+- Pulumi.yaml
+- tsconfig.json
+</FileTree>
 
 ### Configure the stack
 
 Modify your stack configuration in `Pulumi.dev.yaml` to include endpoints for AWS services pointing to `http://localhost:4566`.
 However, these endpoints may change depending on the AWS plugin version you are using.
 
-```yaml
+```yaml showLineNumbers
 config:
   aws:accessKey: test
   aws:s3UsePathStyle: "true"
diff --git a/src/content/docs/aws/integrations/infrastructure-as-code/terraform.mdx b/src/content/docs/aws/integrations/infrastructure-as-code/terraform.mdx
@@ -51,10 +51,11 @@ After installation, you can use the `tflocal` command, which has the same interf
 
 ```bash
 tflocal --help
-{/* <disable-copy> */} {/* mdx-disabled */}
+```
+
+```bash title="Output"
 Usage: terraform [global options] <subcommand> [args]
 ...
-<disable-copy>
 ```
 
 ### Deploy the Terraform configuration
@@ -88,7 +89,6 @@ tflocal apply
 | `AWS_ACCESS_KEY_ID`      | `test` (`accountId`: 000000000000)   | AWS Access Key ID to use for multi-account setups |
 
 :::note
-
 While using `CUSTOMIZE_ACCESS_KEY`, following cases are taking precedence over each other from top to bottom:
 1. If the `AWS_ACCESS_KEY_ID` environment variable is set.
 2. If `access_key` is configured in the Terraform AWS provider.
@@ -144,9 +144,9 @@ Furthermore, it's necessary to configure the individual services to use LocalSta
 For S3, this configuration resembles the following snippet, where we've chosen to use the virtual hosted-style endpoint:
 
 ```hcl
-  endpoints {
-    s3             = "http://s3.localhost.localstack.cloud:4566"
-  }
+endpoints {
+  s3             = "http://s3.localhost.localstack.cloud:4566"
+}
 ```
 
 :::note
@@ -226,7 +226,6 @@ provider "aws" {
 ```
 
 :::note
-
 To heuristically detect whether your Terraform configuration should be deployed against LocalStack, you can use the following snippet:
 
 ```hcl
@@ -414,6 +413,7 @@ Note: You can always add providers using 'cdktf provider add' later on
 <TabItem label="Python">
 ```python
  $ pipenv install cdktf-cdktf-provider-aws
+```
 </TabItem>
 <TabItem label="TypeScript">
 ```javascript
@@ -524,14 +524,15 @@ OpenTofu is an open-source fork of Terraform acting as a drop-in replacement for
 
 ```bash
 TF_CMD=tofu tflocal --help
-<disable-copy>
+```
+
+```bash title="Output"
 Usage: tofu [global options] <subcommand> [args]
 
 The available commands for execution are listed below.
 The primary workflow commands are given first, followed by
 less common or more advanced commands.
 ...
-</disable-copy>
 ```
 
 ## Terragrunt
