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

Accept File Marks for any valid path (via --file-marks-yaml) #553

Open
pivotaljohn opened this issue Nov 25, 2021 · 1 comment
Open

Accept File Marks for any valid path (via --file-marks-yaml) #553

pivotaljohn opened this issue Nov 25, 2021 · 1 comment
Labels
enhancement This issue is a feature request priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence but not planned. Contributions are welcome.

Comments

@pivotaljohn
Copy link
Contributor

Describe the problem/challenge you have
Tool integrators would like the ability to integrate with ytt, accepting paths to files without limitation.
That integration includes the ability to configure processing of sets of files via File Marks.

Today, file marks are supplied via a command-line flag whose argument is of a specific format that uses the : and = characters as delimiters.
These are valid characters for paths on most operating systems.
This means there are valid path names (however uncommon) for which there is no way to configure a file mark.

Describe the solution you'd like
Introduce a new command-line flag: --file-marks-yaml which contains a sequence of file mark-shaped mappings. In this way, any string can be supplied for path.

For example:

$ ytt -f . --file-marks-yaml '[{"path": "conf:ig.yml", "type": "yaml-plain"}]'

This flag should be able to process all known file marks: https://carvel.dev/ytt/docs/latest/file-marks/#docs

Anything else you would like to add:
This request originated with #468.


Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@pivotaljohn pivotaljohn added enhancement This issue is a feature request carvel triage This issue has not yet been triaged for relevance labels Nov 25, 2021
@pivotaljohn pivotaljohn added priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence but not planned. Contributions are welcome. and removed carvel triage This issue has not yet been triaged for relevance labels Nov 25, 2021
@pivotaljohn
Copy link
Contributor Author

While this is not on the roadmap for the core maintainers, if someone would fashion this contribution, we'd happily accept. 👍🏻

@aaronshurley aaronshurley moved this to To Triage in Carvel Aug 18, 2022
@pivotaljohn pivotaljohn moved this from To Triage to Unprioritized in Carvel Sep 27, 2022
@github-project-automation github-project-automation bot moved this to To Triage in Carvel Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This issue is a feature request priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence but not planned. Contributions are welcome.
Projects
Status: To Triage
Development

No branches or pull requests

1 participant