-
Notifications
You must be signed in to change notification settings - Fork 437
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
Target Mode docs #4267
Target Mode docs #4267
Conversation
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
✅ Deploy Preview for chef-web-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: dishanktiwari2501 <dtiwari@progress.com>
Signed-off-by: dishanktiwari2501 <dtiwari@progress.com>
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
content/target_mode.md
Outdated
user = 'root' | ||
password = '123456' | ||
|
||
protocol = ssh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be in single quotes. Otherwise it will give syntax error.
content/target_mode.md
Outdated
user = 'root' | ||
password = '123456' | ||
|
||
protocol = ssh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thing which I want to keep as note here that protocol keyword does not work if using winrm as transport protocol. What works for both ssh and winrm is transport_protocol
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per Thomas H windows will not be supported for target mode. We will have to make that change later . You can make the change mentioned above though. @tpowell-progress
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
PATH="/opt/chefdk/bin:/opt/chefdk/embedded/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" | ||
GEM_ROOT="/opt/chefdk/embedded/lib/ruby/gems/2.6.0" | ||
|
||
0,30 * * * * * chef-runner /usr/bin/chef-client -t <TARGET_NAME> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per my knowledge there is missing peace of information here.
- Where this cron file should be? On node or on host?
- Second when chef-client runs without --local-mode i.e -z option it will check for the client.pem file and client.rb file. That peace of information is missing here. Unless you have client.pem and client.rb file on the host the chef-client run will fail if not running in a local mode.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Vasu1105 Given target mode, I would assume the host is the only one with chef-client, and the usual requirements for chef-client setup would apply. It might be worth calling that out specifically still.
Quality Gate passedIssues Measures |
Description
Add documentation about Target Mode.
Definition of Done
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussion that's relevant]
Related PRs
Check List