Skip to content

fix instructions for init and upgrade with patternizer #621

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 17, 2025
Merged

fix instructions for init and upgrade with patternizer #621

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/blog/2025-07-24-introducing-patternizer.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ Navigate to your repository's root and run the Patternizer container, mounting y
+
[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/hybridcloudpatterns/patternizer init
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init
----
+
This single command scans your repository for Helm charts and generates all the necessary files to turn it into a Validated Pattern.
Expand Down Expand Up @@ -88,7 +88,7 @@ Run the `init` command with the `--with-secrets` flag:

[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/hybridcloudpatterns/patternizer init --with-secrets
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init --with-secrets
----

This command updates your configuration to integrate with External Secrets Operator (ESO) and Vault. It generates a `values-secret.yaml.template` for defining your secrets and automatically adds the required operator subscriptions to your pattern.
Expand Down
10 changes: 5 additions & 5 deletions content/blog/2025-08-29-new-common-makefile-structure.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,14 +67,14 @@ Adopting the new approach is straightforward whether you're bootstrapping a bran
+
[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer init
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init
----
+
Add secrets scaffolding at any time with:
+
[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer init --with-secrets
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer init --with-secrets
----
. Review the changes (`values-*.yaml`, `pattern.sh`, `Makefile`, `Makefile-common`), then commit.
. Try it out:
Expand All @@ -95,7 +95,7 @@ Move from the legacy `common` structure to the new Makefile-driven setup with a

[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer upgrade
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer upgrade
----

What this does:
Expand All @@ -111,7 +111,7 @@ If you prefer to fully replace your `Makefile` with the default version, run:

[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer upgrade --replace-makefile
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer upgrade --replace-makefile
----

After upgrading, commit the changes and use the targets described below (for example, `./pattern.sh make show` or `./pattern.sh make install`).
Expand Down Expand Up @@ -341,7 +341,7 @@ Ready to try it? Run:

[source,bash]
----
podman run -v "$PWD:/repo:z" quay.io/validatedpatterns/patternizer upgrade
podman run --pull=newer -v "$PWD:$PWD:z" -w "$PWD" quay.io/validatedpatterns/patternizer upgrade
----

and commit the changes. Your repo will instantly be on the new path.