-
Notifications
You must be signed in to change notification settings - Fork 25
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
Make output files extension configurable #296
Comments
mergify bot
pushed a commit
that referenced
this issue
Jan 28, 2022
Fixes #296 I've retained the current behavior as the default, and added a prop to `App` to allow configuration of the file extensions applied to the outputted YAML. Please just let me know if you'd like any more information or if I need to make any changes!
Chriscbr
pushed a commit
that referenced
this issue
Jan 28, 2022
Fixes #296 I've retained the current behavior as the default, and added a prop to `App` to allow configuration of the file extensions applied to the outputted YAML. Please just let me know if you'd like any more information or if I need to make any changes! Signed-off-by: Christopher Rybicki <rybickic@amazon.com>
Chriscbr
added a commit
that referenced
this issue
Jan 28, 2022
Fixes #296 I've retained the current behavior as the default, and added a prop to `App` to allow configuration of the file extensions applied to the outputted YAML. Please just let me know if you'd like any more information or if I need to make any changes! Signed-off-by: Christopher Rybicki <rybickic@amazon.com> Co-authored-by: S Heckler <55748928+heckler1@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is something that would be useful for our use case, as it removes the need for renaming files to match existing manifests as a secondary step.
The text was updated successfully, but these errors were encountered: