Skip to content

Commit bc65b06

Browse files
committed
Reduce trips to the PE Console UI
Prior to this commit, I asked users to enabled code manager first then later come back and configure it. After this commit, I ask users to enable and configure code manager at the same time. This cuts out a puppet run and simplifies the instructions
1 parent c7c5f9f commit bc65b06

File tree

1 file changed

+15
-21
lines changed

1 file changed

+15
-21
lines changed

README.md

Lines changed: 15 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -30,33 +30,27 @@ This module was originally a very prescriptive profile in the [puppetlabs-rampup
3030

3131
# Easy Button Setup
3232

33-
1. Enable code manager via the PE Console UI or hiera:
34-
35-
```
36-
puppet_enterprise::profile::master::code_manager_auto_configure: true
37-
```
38-
39-
2. Run `puppet agent -t`
33+
1. Login to the PE console
34+
2. Navigate to the Classification page
35+
- Click on the PE Master group
36+
- Click the Classes tab
37+
- Find the `puppet_enterprise::profile::master` class
38+
- Set the `code_manager_auto_configure` to `true`
39+
- Set the `r10k_remote` to the SSH url of your git repo
40+
- Set the `r10k_private_key` parameter to `/etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa.key`
41+
- Commit your changes
4042

41-
3. Install and run this module:
43+
3. Enable code mananger then install and run this module:
4244

43-
```
45+
~~~
46+
puppet agent -t
4447
puppet module install npwalker-pe_code_manager_webhook
45-
chown -R pe-puppet:pe-puppet /etc/puppetlabs/code/environments/production/modules/
46-
puppet apply -e "include pe_code_manager_webhook"
47-
```
48+
chown -R pe-puppet:pe-puppet /etc/puppetlabs/code/
49+
puppet apply -e "include pe_code_manager_webhook::code_manager"
50+
~~~
4851

4952
4. Configure a deploy key in your Git server using the SSH key created by the module
5053
- You'll paste `cat /etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa.pub`
51-
5. Login to the PE console
52-
6. Navigate to the Classification page
53-
- Click on the PE Master group
54-
- Click the Classes tab
55-
- Find the `puppet_enterprise::profile::master` class
56-
- Set the `r10k_remote` to the SSH url of your git repo
57-
- Set the `r10k_private_key` parameter to `/etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa.key`
58-
- Commit your changes
59-
6. Run `puppet agent -t`
6054
7. Create a webhook on the control-repo repository in your Git server UI
6155
- The URL to connect to code manager is found at `/etc/puppetlabs/puppetserver/.puppetlabs/webhook_url.txt`
6256
8. Assuming this was a new install with no previous code in the code directory then everything worked.

0 commit comments

Comments
 (0)