greentic-deployer 0.4.8

Greentic pack deployer generating multi-cloud IaC + manifests
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

# Provider Artifact Visual Guide

Quick reference for reviewing the generated IaC artifacts per cloud provider. Use this when preparing screenshots or demos.

## Directory Layout

```text
deploy/
└── <provider>/<tenant>/<environment>/
    ├── master.tf|master.bicep|master.yaml
    ├── variables.tf|parameters.json|parameters.yaml
    ├── plan.json
    ├── apply-manifest.json
    └── destroy-manifest.json
```

## AWS (Terraform/OpenTofu)

- Open `master.tf` in any HCL viewer to highlight:
  - `aws_ecs_task_definition` / `aws_ecs_service` blocks per runner.
  - `data "aws_secretsmanager_secret_version"` entries for each logical secret.
- Diagram cheat sheet:

```mermaid
flowchart TD
    A[plan.json] --> B{master.tf}
    B --> C[Secret data sources]
    B --> D[ECS task definitions]
    D --> E[ECS services]
    B --> F[# OAuth / channel comments]
```

- Screenshot tip: fold everything except a single runner block plus the secret data sources.
- Mock reference: ![AWS mock screenshot](images/aws-mock.svg)

## Azure (Bicep)

- Load `master.bicep` in VS Code with the Bicep extension or the Azure portal editor to show tooltips.
- Useful anchors:
  - `param secretPaths object` demonstrates Key Vault wiring.
  - Each `Microsoft.Web/containerApps` resource references telemetry env vars and secrets.

```mermaid
flowchart LR
    P[parameters.json] -->|secretPaths| B[master.bicep]
    B --> CA1[ContainerApp support]
    B --> CA2[ContainerApp ops]
    CA1 --> KV[Key Vault refs]
    CA2 --> KV
```

- Screenshot tip: capture the outline panel plus the `secretPaths` hover tooltip.
- Mock reference: ![Azure mock screenshot](images/azure-mock.svg)

## GCP (Deployment Manager)

- `master.yaml` describes the deployment; `parameters.yaml` contains substitutions.
- Focus on the `env` entries that pull from Secret Manager via `valueFrom.secretKeyRef`.

```mermaid
flowchart TD
    Y[master.yaml] --> Env[Runner environment vars]
    Y --> Secrets[Secret Manager refs]
    Params[parameters.yaml] --> Y
```

- Screenshot tip: show the YAML `env:` block with the secret reference expanded.
- Mock reference: ![GCP mock screenshot](images/gcp-mock.svg)

## Manifests

- `apply-manifest.json` / `destroy-manifest.json` are provider-agnostic summaries:
  - `secrets` → logical name, provider path, byte length.
  - `oauth_clients` → provider ids and redirect URLs.
- Paste them into a JSON viewer and highlight the sections above when walking through a plan/apply flow.