Skip to content
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.

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

gitrepository semver with prefix #1295

Closed
wrenix opened this issue Nov 23, 2023 · 5 comments
Closed

gitrepository semver with prefix #1295

wrenix opened this issue Nov 23, 2023 · 5 comments

Comments

@wrenix
Copy link

wrenix commented Nov 23, 2023

i really like the idea to deploy multiple time the same gitrepo with different tags, e.g. a helmchart repository which stores multiple chart with an prefix.

so an filtering like in imageupdate would be nice:
https://fluxcd.io/flux/guides/image-update/#imagepolicy-examples

so i could use an regex like /^my-chart-v(?<version>\d+\.\d+\.\d+)/

@stefanprodan
Copy link
Member

Helm chart version spec is strict semver, why not push the charts from the repo to your container registry and use those OCI artifacts with Flux?

@wrenix
Copy link
Author

wrenix commented Nov 23, 2023

for helm it would be a good point, what if i like to tag components (which are in folders) based on kustomize

@stefanprodan
Copy link
Member

I have the same answer, push the dir to the container registry using flux push artifact using a semver tag, then use an OCIRepository with a semver range.

@wrenix
Copy link
Author

wrenix commented Nov 24, 2023

for helm it would be a good point, what if i like to tag components (which are in folders) based on kustomize

@wrenix wrenix closed this as completed Nov 24, 2023
@christian-vdz
Copy link

christian-vdz commented Jan 29, 2024

Hello, I have a monorepo which contains multiples applications and I would like to use scoped tags in my gitrepositories.

Example:

  • Git repo app1: semver ~app1@1.0
  • Git repo app2: semver ~app2@1.1.0

I didn't find anyway to do this
New issue: #1354

@wrenix wrenix reopened this Jan 30, 2024
@stefanprodan stefanprodan closed this as not planned Won't fix, can't repro, duplicate, stale Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants