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

Add a C4B role to the collection to license & configure endpoints #53

Open
vexx32 opened this issue Jun 2, 2021 · 1 comment
Open
Assignees
Labels
0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Documentation Issues for changes that only need to change documentation Improvement Issues that enhances existing functionality, or adds new features
Milestone

Comments

@vexx32
Copy link
Member

vexx32 commented Jun 2, 2021

We should have a role for C4B client machines which enables:

  • Licensing
  • Configuration
@vexx32 vexx32 added Improvement Issues that enhances existing functionality, or adds new features 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint labels Jun 2, 2021
@vexx32 vexx32 added this to the 1.2.x milestone Jun 2, 2021
@adilio
Copy link
Contributor

adilio commented Jun 2, 2021

I've written a playbook for this functionality before:
https://github.com/adilio/summit-2021/blob/main/ansible/setup-c4b.yml
It does the following:

  • Install Chocolatey from an internal repo
  • Install Chocolatey license
  • Install Chocolatey licensed packages
  • Enable Chocolatey features & config
  • Check-in to Chocolatey Central Management

Possible addition:

  • Import Chocoserver certificate

@pauby pauby assigned pauby and unassigned adilio Jan 21, 2022
@pauby pauby added the Documentation Issues for changes that only need to change documentation label Jan 21, 2022
@pauby pauby modified the milestones: 1.2.x, 1.x.x Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint Documentation Issues for changes that only need to change documentation Improvement Issues that enhances existing functionality, or adds new features
Projects
None yet
Development

No branches or pull requests

3 participants