Chocolatey bootstrap: Create a possibilty to provision chocolatey via states

[eglipeter]

It would be very nice, if chocolatey could be installed on a minion via a salt sls state file. It should be checked whether chocolatey is installed and if not, the bootstrap function should be called. Most preferably, the version of chocolatey which is installed should chooseable by the admin. Furthermore, it would be nice, if chocolatey could be configured also via such a state module (choco config, https://chocolatey.org/docs/chocolatey-configuration).

Yours,
Peter

[Ch3LL]

how about this? https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html#salt.modules.chocolatey.bootstrap

[vernondcole]

It would be nice if the chocolatey state documentation would give a hint that

choc_boot:
  module.run:
    - name: chocolatey.bootstrap

is available. A cross reference to the execution module would then do the trick.

[Ch3LL]

module.run is available for all execution modules so I don't see it necessary to document just for this execution module. now that i re-read @eglipeter original request I think its best we approve this as a feature request to add a state module around the chocolatey.bootstrap execution module, that way you don't need to use the module.run workaround.

[Ch3LL]

ping @saltstack/team-windows just fyi if anyone is curious enough to tackle this ;)

[aledjones]

Is this issue still under review or has it been ever on your list, @saltstack/team-windows ?
We would really need this to simplify our deployment states for Windows.

[SylvainMartel]

It would be great to add chocolate client installation from an internal source. Bootstrap doesn't help in that scenario.

[muddman]

Also, running the current bootstrap module results in (changed=1) even if it's already installed.

version 2019.2.1

chocolatey_install:
  module.run:
    - chocolatey.bootstrap:

[stale]

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.

[stale]

Thank you for updating this issue. It is no longer marked as stale.