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

[BUG] When calling init.sls via explicit init name, the name is treated as a directory name in context #58250

Closed
mlasevich opened this issue Aug 19, 2020 · 0 comments · Fixed by #58238
Labels
Bug broken, incorrect, or confusing behavior Magnesium Mg release after Na prior to Al severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Milestone

Comments

@mlasevich
Copy link
Contributor

Description

if "init" SLS is access using it's explicit name - i.e. path.to.init instead of path.to - the "init" part shows up as a directory component in various sls* context parmeters

Setup
Set up following file slspath/init.sls:

test:
  test.nop:
    - context:
        slspath: "{{ slspath }}"
        slsdotpath: "{{ slsdotpath }}"
        slscolonpath: "{{ slscolonpath }}"
        sls_path: "{{sls_path}}"

Steps to Reproduce the behavior

Run: salt-call state.show_sls slspath.init --output=yaml

Result:

# [INFO    ] Loading fresh modules for state activity
local:
  test:
    test:
    - context:
        slspath: slspath/init
        slsdotpath: slspath.init
        slscolonpath: slspath:init
        sls_path: slspath_init
    - nop
    - order: 10000
    __sls__: slspath.init
    __env__: base

As you see, "init" becomes a directory name, even though no such directory exists

Expected behavior

Expecting slspath to alway reflect actual path of the sls - i.e. in this case it should be slspath

@mlasevich mlasevich added the Bug broken, incorrect, or confusing behavior label Aug 19, 2020
@sagetherage sagetherage added Magnesium Mg release after Na prior to Al severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around and removed needs-triage labels Sep 23, 2020
@sagetherage sagetherage added this to the Magnesium milestone Sep 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Magnesium Mg release after Na prior to Al severity-medium 3rd level, incorrect or bad functionality, confusing and lacks a work around
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants