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

Support the ability to fork manifests into specific locations of a chart #8

Open
aiyengar2 opened this issue Jan 28, 2021 · 3 comments
Assignees

Comments

@aiyengar2
Copy link
Contributor

Add the following field to Charts and AdditionalCharts to support forking manifests

manifests:
- url: <required> # UpstreamOptions
  subdirectory: <optional> # UpstreamOptions
  commit: <optional> # UpstreamOptions
  filepath: <optional> # a specific file in the subdirectory to pull in the manifest for
  manifestPath: <required> # Where to drop the manifests, directories along path will be created if they don't exist
@aiyengar2 aiyengar2 self-assigned this Jan 28, 2021
@aiyengar2
Copy link
Contributor Author

This feature could be used by Monitoring V2 to maintain the latest manifest for nginx-ingress + traefik as part of https://github.com/rancher/tasks/issues/69.

@aiyengar2
Copy link
Contributor Author

While we cannot fork manifests into a specific location within a chart yet, we will add support for setting manifests as an upstream option.

@aiyengar2
Copy link
Contributor Author

With the new experimental feature in v0.3.x that allows users to point to a manifest to treat as a dummy Helm chart, this would be a great idea to prioritize sometime soon.

@aiyengar2 aiyengar2 modified the milestones: v2.x - Backlog, 0.4.x Jan 28, 2022
@deniseschannon deniseschannon removed this from the 0.4.x milestone Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants