feat: prevent review app specs from being jinja rendered #410
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.
Solves #408
A review app spec does not have to be Jinja rendered because any Jinja template was already rendered when the spec was created during
hokusai review_app setup
. During spec creation, Hokusai copied Staging spec and rendered Jinja templates.When Staging spec has Jinja template escaped with
{% raw %}
, the double rendering causeshokusai review_app create
to break.This PR proposes to eliminate the second rendering. To achieve that, a
render_template
flag is introduced and passed down the call chain. We default it toTrue
so there's no impact on non-review-app commands (e.g.hokusai staging ...
,hokusai production ...
). Review app commands set it toFalse
, so that the review app spec is not rendered.This PR also replaces legacy
test/unit/test_yaml_spec.py
with a Pytest-format version that is more comprehensive.