From 3370f0bdfebf1d753db7a49a039a65b59b3db61a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pawe=C5=82=20Krupa=20=28paulfantom=29?= <pawel@krupa.net.pl>
Date: Tue, 12 Apr 2022 12:37:30 +0200
Subject: [PATCH] *: move sync-to-internal-registry.jsonnet out of TLD

---
 docs/customizations/using-custom-container-registry.md          | 2 +-
 .../sync-to-internal-registry.jsonnet                           | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename sync-to-internal-registry.jsonnet => examples/sync-to-internal-registry.jsonnet (100%)

diff --git a/docs/customizations/using-custom-container-registry.md b/docs/customizations/using-custom-container-registry.md
index f4ffab0b..6d01f8e0 100644
--- a/docs/customizations/using-custom-container-registry.md
+++ b/docs/customizations/using-custom-container-registry.md
@@ -5,7 +5,7 @@ Some Kubernetes installations source all their images from an internal registry.
 To produce the `docker pull/tag/push` commands that will synchronize upstream images to `internal-registry.com/organization` (after having run the `jb` command to populate the vendor directory):
 
 ```shell
-$ jsonnet -J vendor -S --tla-str repository=internal-registry.com/organization sync-to-internal-registry.jsonnet
+$ jsonnet -J vendor -S --tla-str repository=internal-registry.com/organization examples/sync-to-internal-registry.jsonnet
 $ docker pull k8s.gcr.io/addon-resizer:1.8.4
 $ docker tag k8s.gcr.io/addon-resizer:1.8.4 internal-registry.com/organization/addon-resizer:1.8.4
 $ docker push internal-registry.com/organization/addon-resizer:1.8.4
diff --git a/sync-to-internal-registry.jsonnet b/examples/sync-to-internal-registry.jsonnet
similarity index 100%
rename from sync-to-internal-registry.jsonnet
rename to examples/sync-to-internal-registry.jsonnet
-- 
GitLab