Add information about public ca key, access key, and secret key. #4419
Conversation
✅ Deploy Preview for chef-web-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
The SaaS public key instructions here isn't a very good practice with CB writing we should be encouraging. Customers should have choice based on how they choose to approach it to get contents and store in a variable or attribute of wrapper cookbook and just passing it to the resource. I wouldn't recommend actually having any documentation on procedure as that should be documented in CB and we simply reference using the resource from the CB for registration. This way if it needs to change in the future we only have to update CB and not docs here. |
IanMadd
force-pushed
the
im/360_saas_root_ca
branch
from
2c7d769 to
5c1631e
Compare
| @@ -171,29 +230,30 @@ To configure the cookbooks and define enrollment settings, follow these steps: | |||
| - `<CHEF_360_FQDN>` with the fully qualified domain name (FQDN) for your Chef 360 SaaS deployment. | |||
| - `<ENROLLMENT_TYPE>` with either `full` or `partial` depending on the form of enrollment. Use `full` unless you must `partial`. | |||
| - `<API_PORT>` with the API port configured in Chef 360 SaaS. The default value is `31000`. | |||
There was a problem hiding this comment.
@IanMadd API port should be 443 for SaaS
Signed-off-by: Ian Maddaus <[email protected]>
Signed-off-by: Ian Maddaus <[email protected]>
Signed-off-by: Ian Maddaus <[email protected]>
Signed-off-by: Ian Maddaus <[email protected]>
Signed-off-by: Ian Maddaus <[email protected]>
IanMadd
force-pushed
the
im/360_saas_root_ca
branch
from
0ed9441 to
904aa49
Compare
|
Description
Definition of Done
Issues Resolved
Related PRs
Check List