Feat: OutputTemplates #813
Open
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
ofedoren
reviewed
May 31, 2023
| unless processed_output | ||
| return renderer.error_message.html_safe, false | ||
| end | ||
| return processed_output, true |
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.
This patch adds the possibility to process the output of the jobs.
There are two ways to do that:
On top of that, it is possible to set default Output Templates for a Job Template, meaning it would be selected directly when selecting a new Output Template.
Let me add 'How to use' screenshots.
Now, when executing the job, there are new fields in the wizard:
^ There is a slight change now - users can define only one Runtime template. Therefore users do not have to submit:)
When you want to see the output of the job, navigate to the "Processed tab":
This patch will show Runtime templates in the "default Output Templates" multi-select field. A solution for not showing these would be a part of a patch to the Foreman repo.