_xenv option for includes in state files broken #26685
Labels
Bug
broken, incorrect, or confusing behavior
Execution-Module
help-wanted
Community help is needed to resolve this
P3
Priority 3
Platform
Relates to OS, containers, platform-based utilities like FS, system based apps
severity-medium
3rd level, incorrect or bad functionality, confusing and lacks a work around
stale
Milestone
Comments
jfindlay
added
Execution-Module
Bug
|
@icanhazpython, thanks for the report. |
meggiebot
added
Platform
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like there has been a regression. I'm using 2015.5.5, however the issue seems to be present even in the development branch. @tsclausing had made an edit to state.py (1fa275f) mentioned here (#2683) back in 2012. It looks like some part of that commit made it into the present-day state.sls. On the 2015.5.5 tag, state.sls file line 2593, you can see part of his code. However it seems to have been pushed down, in that line 2578 is executed first, which fails with the error seen there if the _xenv dict key is used in the include. It looks like the order of that check would need to be shuffled around to allow the _xenv option to work again.
The text was updated successfully, but these errors were encountered: