Allow configuration of pull path #215
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At present, Grizzly hardwires the directories to which it writes files when pulling. For some use-cases, this means that every file must be introspected in order to establish its purpose. If, instead, it were possible to include additional information from the resource (likely a dashboard) into the filename, decisions could be made without requiring introspection of the file.
This PR adds two features:
grr pull -f "{{.metadata.folder}}-{{.metadata.name}}.yaml"formatting of the path that pull writes to.metadata.annotations.slugannotation to dashboards that is derived from the title. This can make the meaning of the file more evident.