Community Note
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Tell us about your request
Support relative-path references as described by RFC-3986, allowing something similar to --update=file:relative/path/to/config.yml.
This would introduce some new ambiguity鈥攊s that a URI or a YAML string?鈥攂ut not a new form of ambiguity. The CLI already decides to treat file:/not-a-path as a URI rather than as literal configuration. Maybe the right way forward is to let different options be responsible for URIs (which could then just be paths) and literal configuration.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
The same as in #93, reference configuration files by relative path. This would be especially nice to have in collaborative projects that don't necessarily live at the same absolute path for different collaborators.
Are you currently working around this issue?
Yes, with file://$(pwd)/relative/path/to/config.yml
Community Note
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Tell us about your request
Support relative-path references as described by RFC-3986, allowing something similar to
--update=file:relative/path/to/config.yml.This would introduce some new ambiguity鈥攊s that a URI or a YAML string?鈥攂ut not a new form of ambiguity. The CLI already decides to treat
file:/not-a-pathas a URI rather than as literal configuration. Maybe the right way forward is to let different options be responsible for URIs (which could then just be paths) and literal configuration.Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
The same as in #93, reference configuration files by relative path. This would be especially nice to have in collaborative projects that don't necessarily live at the same absolute path for different collaborators.
Are you currently working around this issue?
Yes, with
file://$(pwd)/relative/path/to/config.yml