plinth-cli 0.2.0__tar.gz

plinth_cli-0.2.0/.gitignore

@@ -0,0 +1,8 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+generated/
+dist/
+brag-output*/

plinth_cli-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 dfoshidero
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

plinth_cli-0.2.0/PKG-INFO

@@ -0,0 +1,174 @@
+Metadata-Version: 2.5
+Name: plinth-cli
+Version: 0.2.0
+Summary: Generates local, ready-to-push application and GitOps repositories from one config.
+Project-URL: Homepage, https://github.com/dfoshidero/plinth
+Project-URL: Issues, https://github.com/dfoshidero/plinth/issues
+Author: dfoshidero
+License-Expression: MIT
+License-File: LICENSE
+Keywords: argo-cd,dagger,generator,gitops,monorepo,scaffolding,score
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Code Generators
+Requires-Python: >=3.12
+Requires-Dist: jinja2<4,>=3.1
+Requires-Dist: pydantic<3,>=2.11
+Requires-Dist: pyyaml<7,>=6.0
+Requires-Dist: questionary<3,>=2.1
+Description-Content-Type: text/markdown
+
+# plinth
+
+Generate ready-to-push application and GitOps repositories from one config file.
+
+plinth turns a short `plinth.yaml` into git repositories with working application code, a
+[Dagger](https://dagger.io) CI pipeline, [Score](https://score.dev) workload specs, and an
+[Argo CD](https://argo-cd.readthedocs.io) GitOps repository that deploys them. Start as a
+modular monolith, a set of microservices or a hybrid of both, in one repo or one repo per app,
+and grow later with `plinth add`.
+
+## Install
+
+```sh
+uv tool install plinth-cli      # or: pipx install plinth-cli
+plinth --version
+```
+
+The PyPI package is `plinth-cli`; the command is `plinth`. Requires Python 3.12+.
+
+## Quick start
+
+Answer a few questions:
+
+```sh
+plinth project
+```
+
+or write a config and generate from it:
+
+```yaml
+# plinth.yaml
+project:
+  name: atlas
+  architecture: hybrid          # modular-monolith | microservices | hybrid
+  layout: monorepo              # monorepo | split-repo
+  gitProvider: github           # github | gitlab | generic
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: modular-monolith}
+  - {name: worker, kind: worker}
+  - {name: notifier, kind: service, port: 8081}
+environments: [dev, production]
+```
+
+```sh
+plinth validate --config plinth.yaml
+plinth generate --config plinth.yaml --output .
+```
+
+This writes `./atlas/` containing one folder per repository, each initialised with git, an
+initial commit and an `origin` remote under `gitBaseUrl`. Create the empty repositories on your
+git host and push.
+
+More configs live in [`examples/`](examples/): every architecture with both layouts.
+
+## What you get
+
+**Application repositories** (one for a monorepo, one per app for split-repo):
+
+- a small, dependency-free Python app per workload with a `/health` endpoint (services and the
+  monolith) or a run loop (workers), plus tests; replace it with your own code
+- a `Dockerfile` and a `score.yaml` describing how the workload runs
+- a Dagger module (`.dagger/`) with `test`, `build` and `ship` functions that run identically on
+  your laptop and in CI
+- a CI file for your provider (`.github/workflows/ci.yaml` or `.gitlab-ci.yml`) that tests pull
+  requests and ships `main`
+
+**A GitOps repository:**
+
+- an Argo CD app-of-apps (`bootstrap/root.yaml`) and one ApplicationSet per environment
+- a Helm chart that deploys any workload straight from its `score.yaml`
+- per-environment values, and `release.yaml` files written by CI on every ship
+- `scripts/bootstrap-local.sh` to run everything on a local [k3d](https://k3d.io) cluster
+
+The flow: push to `main` → CI tests, builds and pushes images tagged with the commit → CI writes
+`environments/dev/<workload>/release.yaml` → Argo CD deploys it. Promote by copying a
+`release.yaml` to another environment.
+
+## Grow a project
+
+Add a service or worker to a generated project:
+
+```sh
+cd atlas
+plinth add service billing --port 8090
+plinth add worker mailer
+```
+
+plinth creates the new workload's files (and a new repository for split-repo layouts) and
+updates `plinth.yaml`. Adding to a modular monolith turns it into a hybrid. Existing files are
+never overwritten; any that plinth would now generate differently are listed for you to review.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `plinth project [--output DIR]` | interactive questions, then generate |
+| `plinth validate --config FILE` | check a config and show the repositories it produces |
+| `plinth generate --config FILE --output DIR [--dry-run]` | write the repositories |
+| `plinth add {service,worker} NAME [--port N]` | add a workload to an existing project |
+
+`--no-git` skips `git init` and the initial commit.
+
+## Configuration
+
+| Key | Notes |
+|---|---|
+| `project.name` | kebab-case, 2-30 chars; prefixes every repository name |
+| `project.architecture` | `modular-monolith` (one monolith), `microservices` (services/workers only), `hybrid` (one monolith plus services/workers) |
+| `project.layout` | `monorepo` (`<name>-app` holds every workload) or `split-repo` (`<name>-<app>` each) |
+| `project.gitProvider` | picks the CI file; `generic` generates none |
+| `project.gitBaseUrl` | `https://host/org` the repositories live under |
+| `project.registry` | `host/path` images are pushed to |
+| `applications[]` | `name`, `kind` (`modular-monolith`, `service`, `worker`), optional `port` for HTTP kinds |
+| `environments` | must include `dev`, which CI releases to |
+
+Defaults and pinned tool versions are in [`plinth/config.py`](plinth/config.py).
+
+## When not to use plinth
+
+- You only need a single repository from a template: [Copier](https://copier.readthedocs.io)
+  or [Cookiecutter](https://cookiecutter.readthedocs.io) are simpler, and Copier can update
+  projects later.
+- You already run [Backstage](https://backstage.io): its software templates fit better there.
+- You don't deploy to Kubernetes: the GitOps half won't help you.
+
+plinth generates once. It does not keep generated repositories in sync with newer templates;
+after generation the code is yours.
+
+## Development
+
+```sh
+uv sync
+uv run pytest
+uv run ruff check . && uv run ruff format --check .
+```
+
+Templates live in [`plinth/blueprints/`](plinth/blueprints/). Files ending in `.j2` are rendered
+with Jinja; path segments starting with `dot-` are written with a leading `.`.
+
+## Contributing
+
+Contributions are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md) first; in short, open an
+issue before large changes, and every contribution must be written by a human (no AI-generated
+code or text).
+
+## License
+
+[MIT](LICENSE)

plinth_cli-0.2.0/README.md

@@ -0,0 +1,150 @@
+# plinth
+
+Generate ready-to-push application and GitOps repositories from one config file.
+
+plinth turns a short `plinth.yaml` into git repositories with working application code, a
+[Dagger](https://dagger.io) CI pipeline, [Score](https://score.dev) workload specs, and an
+[Argo CD](https://argo-cd.readthedocs.io) GitOps repository that deploys them. Start as a
+modular monolith, a set of microservices or a hybrid of both, in one repo or one repo per app,
+and grow later with `plinth add`.
+
+## Install
+
+```sh
+uv tool install plinth-cli      # or: pipx install plinth-cli
+plinth --version
+```
+
+The PyPI package is `plinth-cli`; the command is `plinth`. Requires Python 3.12+.
+
+## Quick start
+
+Answer a few questions:
+
+```sh
+plinth project
+```
+
+or write a config and generate from it:
+
+```yaml
+# plinth.yaml
+project:
+  name: atlas
+  architecture: hybrid          # modular-monolith | microservices | hybrid
+  layout: monorepo              # monorepo | split-repo
+  gitProvider: github           # github | gitlab | generic
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: modular-monolith}
+  - {name: worker, kind: worker}
+  - {name: notifier, kind: service, port: 8081}
+environments: [dev, production]
+```
+
+```sh
+plinth validate --config plinth.yaml
+plinth generate --config plinth.yaml --output .
+```
+
+This writes `./atlas/` containing one folder per repository, each initialised with git, an
+initial commit and an `origin` remote under `gitBaseUrl`. Create the empty repositories on your
+git host and push.
+
+More configs live in [`examples/`](examples/): every architecture with both layouts.
+
+## What you get
+
+**Application repositories** (one for a monorepo, one per app for split-repo):
+
+- a small, dependency-free Python app per workload with a `/health` endpoint (services and the
+  monolith) or a run loop (workers), plus tests; replace it with your own code
+- a `Dockerfile` and a `score.yaml` describing how the workload runs
+- a Dagger module (`.dagger/`) with `test`, `build` and `ship` functions that run identically on
+  your laptop and in CI
+- a CI file for your provider (`.github/workflows/ci.yaml` or `.gitlab-ci.yml`) that tests pull
+  requests and ships `main`
+
+**A GitOps repository:**
+
+- an Argo CD app-of-apps (`bootstrap/root.yaml`) and one ApplicationSet per environment
+- a Helm chart that deploys any workload straight from its `score.yaml`
+- per-environment values, and `release.yaml` files written by CI on every ship
+- `scripts/bootstrap-local.sh` to run everything on a local [k3d](https://k3d.io) cluster
+
+The flow: push to `main` → CI tests, builds and pushes images tagged with the commit → CI writes
+`environments/dev/<workload>/release.yaml` → Argo CD deploys it. Promote by copying a
+`release.yaml` to another environment.
+
+## Grow a project
+
+Add a service or worker to a generated project:
+
+```sh
+cd atlas
+plinth add service billing --port 8090
+plinth add worker mailer
+```
+
+plinth creates the new workload's files (and a new repository for split-repo layouts) and
+updates `plinth.yaml`. Adding to a modular monolith turns it into a hybrid. Existing files are
+never overwritten; any that plinth would now generate differently are listed for you to review.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `plinth project [--output DIR]` | interactive questions, then generate |
+| `plinth validate --config FILE` | check a config and show the repositories it produces |
+| `plinth generate --config FILE --output DIR [--dry-run]` | write the repositories |
+| `plinth add {service,worker} NAME [--port N]` | add a workload to an existing project |
+
+`--no-git` skips `git init` and the initial commit.
+
+## Configuration
+
+| Key | Notes |
+|---|---|
+| `project.name` | kebab-case, 2-30 chars; prefixes every repository name |
+| `project.architecture` | `modular-monolith` (one monolith), `microservices` (services/workers only), `hybrid` (one monolith plus services/workers) |
+| `project.layout` | `monorepo` (`<name>-app` holds every workload) or `split-repo` (`<name>-<app>` each) |
+| `project.gitProvider` | picks the CI file; `generic` generates none |
+| `project.gitBaseUrl` | `https://host/org` the repositories live under |
+| `project.registry` | `host/path` images are pushed to |
+| `applications[]` | `name`, `kind` (`modular-monolith`, `service`, `worker`), optional `port` for HTTP kinds |
+| `environments` | must include `dev`, which CI releases to |
+
+Defaults and pinned tool versions are in [`plinth/config.py`](plinth/config.py).
+
+## When not to use plinth
+
+- You only need a single repository from a template: [Copier](https://copier.readthedocs.io)
+  or [Cookiecutter](https://cookiecutter.readthedocs.io) are simpler, and Copier can update
+  projects later.
+- You already run [Backstage](https://backstage.io): its software templates fit better there.
+- You don't deploy to Kubernetes: the GitOps half won't help you.
+
+plinth generates once. It does not keep generated repositories in sync with newer templates;
+after generation the code is yours.
+
+## Development
+
+```sh
+uv sync
+uv run pytest
+uv run ruff check . && uv run ruff format --check .
+```
+
+Templates live in [`plinth/blueprints/`](plinth/blueprints/). Files ending in `.j2` are rendered
+with Jinja; path segments starting with `dot-` are written with a leading `.`.
+
+## Contributing
+
+Contributions are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md) first; in short, open an
+issue before large changes, and every contribution must be written by a human (no AI-generated
+code or text).
+
+## License
+
+[MIT](LICENSE)

plinth_cli-0.2.0/examples/hybrid-monorepo/plinth.yaml

@@ -0,0 +1,12 @@
+project:
+  name: atlas
+  architecture: hybrid
+  layout: monorepo
+  gitProvider: github
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: modular-monolith}
+  - {name: worker, kind: worker}
+  - {name: notifier, kind: service, port: 8081}
+environments: [dev, production]

plinth_cli-0.2.0/examples/hybrid-split-repo/plinth.yaml

@@ -0,0 +1,12 @@
+project:
+  name: atlas
+  architecture: hybrid
+  layout: split-repo
+  gitProvider: github
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: modular-monolith}
+  - {name: worker, kind: worker}
+  - {name: notifier, kind: service, port: 8081}
+environments: [dev, production]

plinth_cli-0.2.0/examples/microservices-monorepo/plinth.yaml

@@ -0,0 +1,12 @@
+project:
+  name: atlas
+  architecture: microservices
+  layout: monorepo
+  gitProvider: github
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: service}
+  - {name: worker, kind: worker}
+  - {name: notifier, kind: service, port: 8081}
+environments: [dev, production]

plinth_cli-0.2.0/examples/microservices-split-repo/plinth.yaml

@@ -0,0 +1,12 @@
+project:
+  name: atlas
+  architecture: microservices
+  layout: split-repo
+  gitProvider: github
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: service}
+  - {name: worker, kind: worker}
+  - {name: notifier, kind: service, port: 8081}
+environments: [dev, production]

plinth_cli-0.2.0/examples/modular-monolith-monorepo/plinth.yaml

@@ -0,0 +1,10 @@
+project:
+  name: atlas
+  architecture: modular-monolith
+  layout: monorepo
+  gitProvider: github
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: modular-monolith}
+environments: [dev, production]

plinth_cli-0.2.0/examples/modular-monolith-split-repo/plinth.yaml

@@ -0,0 +1,10 @@
+project:
+  name: atlas
+  architecture: modular-monolith
+  layout: split-repo
+  gitProvider: github
+  gitBaseUrl: https://github.com/acme
+  registry: ghcr.io/acme
+applications:
+  - {name: api, kind: modular-monolith}
+environments: [dev, production]

plinth_cli-0.2.0/plinth/__init__.py

@@ -0,0 +1 @@
+"""plinth: generate ready-to-push application and GitOps repositories from one config."""

plinth_cli-0.2.0/plinth/__main__.py

@@ -0,0 +1,5 @@
+import sys
+
+from plinth.cli import main
+
+sys.exit(main())

plinth_cli-0.2.0/plinth/add.py

@@ -0,0 +1,97 @@
+"""`plinth add`: grow an existing project with a new service or worker.
+
+Only files that belong to the new workload are created. Existing files are never
+overwritten; ones that plinth would now generate differently are reported so the
+user can review them.
+"""
+
+from __future__ import annotations
+
+from dataclasses import dataclass, field
+from pathlib import Path
+
+from plinth import config as defaults
+from plinth.loader import ConfigError, config_to_dict, dump_config, load_config, parse_config
+from plinth.plan import build_plan
+from plinth.render import render_plan
+from plinth.schema import AppKind, Architecture, ProjectConfig
+from plinth.write import init_repo, write_tree
+
+
+@dataclass
+class AddResult:
+    config: ProjectConfig
+    created: list[str] = field(default_factory=list)
+    kept: list[str] = field(default_factory=list)
+    new_repos: list[str] = field(default_factory=list)
+    notes: list[str] = field(default_factory=list)
+    warnings: list[str] = field(default_factory=list)
+
+
+def add_application(
+    project_dir: Path, kind: AppKind, name: str, port: int | None = None, init_git: bool = True
+) -> AddResult:
+    config_path = project_dir / defaults.CONFIG_FILENAME
+    old = load_config(config_path)
+    data = config_to_dict(old)
+    notes = []
+
+    if kind is AppKind.MODULAR_MONOLITH:
+        raise ConfigError("a project has exactly one modular-monolith; add a service or worker")
+    if old.project.architecture is Architecture.MODULAR_MONOLITH:
+        data["project"]["architecture"] = Architecture.HYBRID.value
+        notes.append("architecture changed from modular-monolith to hybrid")
+
+    app = {"name": name, "kind": kind.value}
+    if port is not None:
+        app["port"] = port
+    data["applications"].append(app)
+    new = parse_config(data, source=str(config_path))
+
+    old_plan, new_plan = build_plan(old), build_plan(new)
+    old_folders = {r.folder for r in old_plan.repos}
+    files = render_plan(new_plan)
+    result = AddResult(config=new, notes=notes)
+
+    new_repos = [r for r in new_plan.repos if r.folder not in old_folders]
+    for repo in new_repos:
+        if (project_dir / repo.folder).exists():
+            raise ConfigError(f"cannot create repository folder, it already exists: {repo.folder}")
+
+    owned = _new_workload_prefixes(new_plan, name)
+    to_write = {}
+    for rel, content in sorted(files.items()):
+        folder = rel.split("/", 1)[0]
+        dest = project_dir / rel
+        if folder not in old_folders or rel.startswith(owned):
+            if dest.exists():
+                if dest.read_bytes() != content:
+                    result.kept.append(rel)
+                continue
+            to_write[rel] = content
+            result.created.append(rel)
+        elif dest.exists() and dest.read_bytes() != content:
+            result.kept.append(rel)
+
+    write_tree(project_dir, to_write)
+    config_path.write_text(dump_config(new), encoding="utf-8")
+
+    for repo in new_repos:
+        result.new_repos.append(repo.folder)
+        if init_git:
+            warning = init_repo(project_dir / repo.folder, repo.url)
+            if warning:
+                result.warnings.append(warning)
+    return result
+
+
+def _new_workload_prefixes(plan, name: str) -> tuple[str, ...]:
+    prefixes = [
+        f"{repo.folder}/{wl.source_dir}"
+        for repo, wl in plan.workloads()
+        if wl.name == name and wl.source_dir
+    ]
+    prefixes += [
+        f"{plan.gitops.folder}/environments/{env}/{name}/" for env in plan.config.environments
+    ]
+    return tuple(prefixes)

plinth_cli-0.2.0/plinth/blueprints/ci/github/dot-github/workflows/ci.yaml.j2

@@ -0,0 +1,38 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+  packages: write
+
+jobs:
+  ci:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {{ defaults.CHECKOUT_ACTION }}
+
+      - name: Test
+        if: github.event_name == 'pull_request'
+        uses: {{ defaults.DAGGER_GITHUB_ACTION }}
+        with:
+          version: "{{ defaults.DAGGER_VERSION }}"
+          call: test
+
+      - name: Ship
+        if: github.event_name == 'push'
+        uses: {{ defaults.DAGGER_GITHUB_ACTION }}
+        env:
+          REGISTRY_PASSWORD: {{ "${{ secrets.REGISTRY_PASSWORD || secrets.GITHUB_TOKEN }}" }}
+          GITOPS_TOKEN: {{ "${{ secrets.GITOPS_TOKEN }}" }}
+        with:
+          version: "{{ defaults.DAGGER_VERSION }}"
+          call: >-
+            ship
+            --commit={{ "${{ github.sha }}" }}
+            --registry-username={{ "${{ vars.REGISTRY_USERNAME || github.actor }}" }}
+            --registry-password=env://REGISTRY_PASSWORD
+            --git-token=env://GITOPS_TOKEN

plinth_cli-0.2.0/plinth/blueprints/ci/gitlab/dot-gitlab-ci.yml.j2

@@ -0,0 +1,36 @@
+stages: [test, ship]
+
+.dagger:
+  image: {{ defaults.DOCKER_IMAGE }}
+  services:
+    - {{ defaults.DOCKER_IMAGE }}-dind
+  variables:
+    DOCKER_HOST: tcp://docker:2376
+    DOCKER_TLS_CERTDIR: /certs
+    DOCKER_TLS_VERIFY: "1"
+    DOCKER_CERT_PATH: /certs/client
+    DAGGER_VERSION: "{{ defaults.DAGGER_VERSION }}"
+  before_script:
+    - apk add --no-cache curl
+    - curl -fsSL https://dl.dagger.io/dagger/install.sh | BIN_DIR=/usr/local/bin sh
+
+test:
+  extends: .dagger
+  stage: test
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
+  script:
+    - dagger call test
+
+ship:
+  extends: .dagger
+  stage: ship
+  rules:
+    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
+  script:
+    - >-
+      dagger call ship
+      --commit=$CI_COMMIT_SHA
+      --registry-username=$REGISTRY_USERNAME
+      --registry-password=env://REGISTRY_PASSWORD
+      --git-token=env://GITOPS_TOKEN

plinth_cli-0.2.0/plinth/blueprints/gitops/applicationset.yaml.j2

@@ -0,0 +1,46 @@
+apiVersion: argoproj.io/v1alpha1
+kind: ApplicationSet
+metadata:
+  name: {{ project.name }}-{{ environment }}
+  namespace: argocd
+spec:
+  goTemplate: true
+  goTemplateOptions: ["missingkey=error"]
+  generators:
+    - git:
+        repoURL: {{ repo.url }}
+        revision: HEAD
+        files:
+          - path: environments/{{ environment }}/*/release.yaml
+  template:
+    metadata:
+      name: '{{ project.name }}-{% raw %}{{ .workload }}{% endraw %}-{{ environment }}'
+    spec:
+      project: {{ project.name }}
+      destination:
+        server: https://kubernetes.default.svc
+        namespace: {{ project.name }}-{{ environment }}
+      sources:
+        - repoURL: {{ repo.url }}
+          targetRevision: HEAD
+          path: charts/workload
+          helm:
+            releaseName: '{% raw %}{{ .workload }}{% endraw %}'
+            valueFiles:
+              - '$app/{% raw %}{{ .scorePath }}{% endraw %}'
+              - '$gitops/environments/{{ environment }}/{% raw %}{{ .workload }}{% endraw %}/values.yaml'
+            parameters:
+              - name: image
+                value: '{% raw %}{{ .image }}{% endraw %}'
+        - repoURL: '{% raw %}{{ .appRepoURL }}{% endraw %}'
+          targetRevision: '{% raw %}{{ .revision }}{% endraw %}'
+          ref: app
+        - repoURL: {{ repo.url }}
+          targetRevision: HEAD
+          ref: gitops
+      syncPolicy:
+        automated:
+          prune: false
+          selfHeal: true
+        syncOptions:
+          - CreateNamespace=true

plinth_cli-0.2.0/plinth/blueprints/gitops/values.yaml.j2

@@ -0,0 +1,2 @@
+# {{ workload.name }} in {{ environment }}. Merged over the workload's score.yaml.
+replicas: {{ defaults.REPLICAS.get(environment, defaults.DEFAULT_REPLICAS) }}