making vars for gitea chart repo and zarf injector #3752
Conversation
✅ Deploy Preview for zarf-docs canceled.
|
Signed-off-by: Omar Ahmad <chiqomar@hotmail.com>
chiqomar
force-pushed
the
configurable-gitea-chart-and-injector-url
branch
from
bceee25 to
f2a877c
Compare
| @@ -6,6 +6,7 @@ agent_image_tag = 'local' | |||
|
|
|||
| # Tag for the zarf injector binary to use | |||
| injector_version = '2025-03-24' | |||
| injector_domain = 'zarf-init-resources.s3.us-east-1.amazonaws.com' | |||
There was a problem hiding this comment.
When I execute zarf dev inspect definition . at the root of the repository - I get the following for the injector
- name: zarf-injector
description: |
Bootstraps a Kubernetes cluster by cloning a running pod in the cluster and hosting the registry image.
Removed and destroyed after the Zarf Registry is self-hosting the registry image.
required: true
only:
cluster:
architecture: arm64
files:
- source: packages/zarf-registry/https:/zarf-init-resources.s3.us-east-1.amazonaws.com/injector/2025-03-24/zarf-injector-arm64
shasum: f68cf097ace34bdd04f6b1571a8d8ab4e04a27614dd7e752199ff09e21f4089b
target: "###ZARF_TEMP###/zarf-injector"
executable: trueWe need to determine why this is malformed.
There was a problem hiding this comment.
Looks like it's adding prepending the source path with the path to the imported package, without first checking if the file is a URL
There was a problem hiding this comment.
Ah because templating happens after imports, Zarf doesn't see the file as a URL during imports and therefore adds the path to the imported component
There was a problem hiding this comment.
Created #3762 as the believed issue preventing this work from completion. We'll get it on our backlog - otherwise feel free to experiment with solutions in the PR if interested.
Co-authored-by: Brandt Keller <43887158+brandtkeller@users.noreply.github.com> Signed-off-by: Omar Ahmad <chiqomar@hotmail.com>
Description
Makes the gitea helm chart path (dl.gitea.io/charts) and the path to the zarf injector binary (zarf-init-resources.s3.us-east-1.amazonaws.com) variables in zarf-config.toml, so that we replace them as necessary, like other paths already can.
Related Issue
Fixes #3722
Checklist before merging