You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
win_pkg.genrepo does not pass saltenv to template.compile_template
While investigating an issue and digging in the code we found the function win_pkg.genrepo() calls win_pkg._repo_process_pkg_sls() which in turn call templates.compile_template().
While win_pkg.genrepo() and templates.compile_template() support an argument saltenv, the function win_pkg._repo_process_pkg_sls() does not, and therefore does not passed the desired saltenv to templates.compile_template()
Request:
This an issue when using the saltenv jinja2 variable within the repo-ng package descriptions and may be an issue when using pillarenvs. Request is to pass the variable properly.
Description
win_pkg.genrepo does not pass saltenv to template.compile_template
While investigating an issue and digging in the code we found the function
win_pkg.genrepo()
callswin_pkg._repo_process_pkg_sls()
which in turn calltemplates.compile_template()
.While
win_pkg.genrepo()
andtemplates.compile_template()
support an argumentsaltenv
, the functionwin_pkg._repo_process_pkg_sls()
does not, and therefore does not passed the desiredsaltenv
totemplates.compile_template()
Request:
This an issue when using the saltenv jinja2 variable within the repo-ng package descriptions and may be an issue when using pillarenvs. Request is to pass the variable properly.
Setup
Any Windows minion affected.
Steps to Reproduce the behavior
Have a package description
Run
Find that a package install fails, because there is no file
C:/store/banana_base.msi
as requested.Expected behavior
The passed saltenv shall be used when rendering win repo-ng package descriptions
Versions Report
salt --versions-report
Additional context
salt/salt/modules/win_pkg.py
Line 1156 in 676e3c0
salt/salt/modules/win_pkg.py
Line 1199 in 676e3c0
salt/salt/modules/win_pkg.py
Line 1210 in 676e3c0
The text was updated successfully, but these errors were encountered: