-
Notifications
You must be signed in to change notification settings - Fork 94
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
Rose conf.read jinja2 #3913
Rose conf.read jinja2 #3913
Conversation
49c5d78
to
b7df1ce
Compare
Do you plan to get this working for Also, |
Yes. |
a89ea8d
to
f37b424
Compare
42e834f
to
699343e
Compare
fafcee2
to
84703f8
Compare
ec3596d
to
4e15e5e
Compare
I've converted this back to a draft PR having decided to steam 🚂 on into dealing with empy, fileinstall and environment variables. |
771c256
to
0aef19d
Compare
5f443ab
to
58fb759
Compare
|
||
|
||
def lion(): | ||
raise TerriblePunException("This is a Lion's Main script") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait until you hear about
count_of = 0
for i in monte_christo:
count_of += 1
@TomekTrzeciak some follow on work captured in these issues otherwise this should be done.
|
Code looks good, need to go through and test again but not expecting any surprises. |
Thanks everyone for perseverance on this one, I think the final result is better for it. One more thing: I think the suggestion to consolidate jinja2/empy code paths #3913 (comment) is still worth doing at some point, but it would require altering |
Can do, tag it against |
What's the plan for replacement of |
Will stay as
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM assuming tests pass
Tests now passing, will have a final test |
Commits will need rationalising pre-merge. |
stub tests for rose fileinstall added cylc install and functional test added check that hash is in flow.cylc if reqd. added rose vars to environment for scheduler.
Removed literal_eval - it's now in the Rose-plugin. Removed writing Environment vars to scheduler environment as the plugin now does this. Assertation Error -> Assertion Error. Added Oliver's through Jinja2 functional test. added the pre_install step to the install script
…empy added Oliver's suggestion about multiple plugins fail if empy/jinja2 section in suite.conf and wrong shebang line refactor fileparse logic added export XYZ to jinja2 test
make sure that template_vars is always available attempt to make template variables safe Update cylc/flow/parsec/fileparse.py Co-authored-by: Oliver Sanders <[email protected]> Apply suggestions from code review added validate step to rose conf tests re-add warning if templates vars will be over-written fromt he CLI fail horribly if multiple plugins clash added test to demonstrate that you can't conflict the templating engine in the plugin. Fixed failure to provide env vars in install pre_configure: test entry point fixes to review items
ff33ce1
to
955eca2
Compare
@oliver-sanders down to 9 ok? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳
These changes address #3819
Summary of Changes
cylc.configure
entry point to parse variables for Cylc incylc/flow/parsec/fileparse.py
.cylc install
which installs files listed inrose-suite.conf
usingcylc.install
entry point.rose-cylc
plugin is installed, but it's probably ok, for now)CYLC_VERSION
jinja2 variable (not to be confused with env varenviron['CYLC_VERSION']
(which might not be set at all))I have not raised a warning for absence of
root-dir
- I think that this needs to be in the plugin.Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.rose-suite.conf
reading functionality, but cannot check the optional config reading until it's plumbed into the CLI