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
First, currently watchmaker has a Yum worker that knows how to retrieve a yum repo file and drop it into /etc/yum.repo.d. Consider introducing a more abstract approach that would support different platforms (e.g. Ubuntu). Alternatively, could use a worker per pkg manager (as now), and require the user to provide a config specific to the platform they are executing against.
Second, the SaltWorker currently calls yum directly to install required pkgs. Consider a function that calls the correct pkg manager according to platform, e.g. yum vs apt... Same alternative here, implement the pkg manager method directly in the salt worker (it is already implemented as the install_method argument), require the user to provide a config specific to the platform the are running against.
The text was updated successfully, but these errors were encountered:
Ok… Reading description-text seems to be focused on enabling only for further Linux distros (ones that don't use RPM-delivered content)? Keeping this open because it's actually (now) meant more for adding packaging-support for Windows?
First, currently watchmaker has a
Yum
worker that knows how to retrieve a yum repo file and drop it into /etc/yum.repo.d. Consider introducing a more abstract approach that would support different platforms (e.g. Ubuntu). Alternatively, could use a worker per pkg manager (as now), and require the user to provide a config specific to the platform they are executing against.Second, the SaltWorker currently calls
yum
directly to install required pkgs. Consider a function that calls the correct pkg manager according to platform, e.g.yum
vsapt
... Same alternative here, implement the pkg manager method directly in the salt worker (it is already implemented as theinstall_method
argument), require the user to provide a config specific to the platform the are running against.The text was updated successfully, but these errors were encountered: