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

Wildcards when support using K8s manifests #2814

Open
jastBytes opened this issue Aug 1, 2024 · 1 comment
Open

Wildcards when support using K8s manifests #2814

jastBytes opened this issue Aug 1, 2024 · 1 comment
Labels
enhancement ✨ New feature or request good first issue 🥇 Good for newcomers

Comments

@jastBytes
Copy link

Is your feature request related to a problem? Please describe.

It is pretty exhausting to specify many K8s manifests in the zarf.yaml. I end up using find to get all paths together.

Describe the solution you'd like

  • Given you have a folder called manifests with all K8s manifests relative to your zarf.yaml
  • When you secify the following in your zarf.yaml:
components:
  - name: manifests
    required: true
    manifests:
      - name: manifests
        namespace: default
        files:
          - manifests/**/*.yaml
  • Then all files with extension .yaml within manifests and all of it's subfolders should be in the package on create.
@jastBytes jastBytes added the enhancement ✨ New feature or request label Aug 1, 2024
@AustinAbro321 AustinAbro321 added the good first issue 🥇 Good for newcomers label Aug 1, 2024
@AustinAbro321
Copy link
Contributor

This would probably be reasonably easy to accomplish with filepath.Glob

@mkcp mkcp added this to Zarf Mar 3, 2025
@github-project-automation github-project-automation bot moved this to Triage in Zarf Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request good first issue 🥇 Good for newcomers
Projects
Status: Triage
Development

No branches or pull requests

2 participants