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

Remove combined-yaml file #346

Open
thomas-robinson opened this issue Feb 7, 2025 · 0 comments
Open

Remove combined-yaml file #346

thomas-robinson opened this issue Feb 7, 2025 · 0 comments

Comments

@thomas-robinson
Copy link
Member

Is your feature request related to a problem? Please describe.
Creating a combined yaml is necessary to facilitate filling is reusable "variables". However, created an extra file and leaving it in a folder is not a good solution. Users will potentially create their own monolithic combined yamls, edit the combined yaml creating an untrackable situation, accidentally push the combined yaml to the repository, or any other of a myriad of possibilities.

Instead of creating a combined yaml file and outputting it into a user's directory (and leaving it there), the yaml should be constructed into a string within fre and then the internal string can be parsed. This avoids I/O to disk and leaving behind an artifact that is unwanted.

Describe the solution you'd like
Combining of the yaml to be done internally instead of by creating an external file and then reading in the file created. This is inefficient.

Describe alternatives you've considered

Additional context

singhd789 pushed a commit that referenced this issue Feb 10, 2025
- instead read yaml info as strings
- append strings to combine yaml information across yamls
- load combined yaml info string
- split up compile and pp classes to make script simpler and easier to follow
singhd789 pushed a commit that referenced this issue Feb 11, 2025
singhd789 pushed a commit that referenced this issue Feb 11, 2025
- `output` option would dump final, cleaned yaml info to a file
singhd789 pushed a commit that referenced this issue Feb 11, 2025
singhd789 pushed a commit that referenced this issue Feb 11, 2025
singhd789 pushed a commit that referenced this issue Feb 13, 2025
- Multiple scripts rely/use this tool
- PR would be too big if I tried to fix each one with this reworked tool
singhd789 pushed a commit that referenced this issue Feb 13, 2025
- this file wouldn't exist anymore
singhd789 pushed a commit that referenced this issue Feb 13, 2025
singhd789 pushed a commit that referenced this issue Feb 14, 2025
- outputs a combined yaml file for other tools to use/reference
singhd789 pushed a commit that referenced this issue Feb 19, 2025
singhd789 pushed a commit that referenced this issue Feb 19, 2025
- other tools also need to be changed with these PR changes so this older script is kept to not break multiple tools
singhd789 pushed a commit that referenced this issue Feb 19, 2025
singhd789 pushed a commit that referenced this issue Feb 20, 2025
singhd789 pushed a commit that referenced this issue Feb 24, 2025
singhd789 pushed a commit that referenced this issue Feb 24, 2025
singhd789 added a commit that referenced this issue Feb 26, 2025
singhd789 added a commit that referenced this issue Feb 26, 2025
- also fix logging messages
singhd789 added a commit that referenced this issue Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant