| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This will allow bootstrap to work with systems
that have `requiretty` configured, and is consistent
with the behavior of Chef 14 bootstrap
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Add license CLI options to chef-apply command
|
| |
| |
| |
| |
| |
| | |
Our major CLI commands should all have this
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
You could accept the license interactively but you could not do it via
the CLI flag
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Bump train-core to 2.1.2
|
|/
|
|
|
|
| |
This pull request was triggered automatically via Expeditor when train-core 2.1.2 was promoted to Rubygems.
This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Multiple Bootstrap bug fixes
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This includes a few fixes:
1. properly handle the default value for session_timeout in cases where
merge_config is not called (plugins) to populate defaults.
2. verify that we're using the ssh protoocl before referencing ssh
constants.
3. capture and compare the higher-level Train::Error for the check
to see if we've gotten a missing fingerprint error, instead of using
Train::Transports::SSHFailed which may not be loaded when exception
is being evaluated.
4. Add tests for missing fingerprint behavior
5. do not save session_timeout to Chef::Config[:knife], it was not
referenced as knife config in any location and we're trying to move away
from pushing CLI values into knife config.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Bump license-acceptance to 1.0.11 to resolve failures on Windows 2016
|
| | |
| | |
| | |
| | | |
Signed-off-by: Aaron Walker <aaronpwalker@gmail.com>
|
| | |
| | |
| | |
| | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \
| |/ /
|/| | |
Update habitat/plan.sh to allow building of Chef Infra Client 15
|
| | |
| | |
| | |
| | | |
Signed-off-by: Scott Macfarlane <smacfarlane@chef.io>
|
|/ /
| |
| |
| | |
Signed-off-by: Scott Macfarlane <smacfarlane@chef.io>
|
|\ \
| | |
| | | |
Chef Infra Client 15 Release Notes copyedits
|
|/ /
| |
| |
| | |
Signed-off-by: Mary Jinglewski <mjinglewski@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Bump license-acceptance to 1.0.8 to resolve failures on Windows 2012R2
|
| |/
| |
| |
| |
| |
| | |
This pull request was triggered automatically via Expeditor when license-acceptance 1.0.8 was promoted to Rubygems.
This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
|
|\ \
| |/
|/| |
Disable AngryChef builds and promotions
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Releng has decided it's best to stop building/promoting AngryChef right
alongside Chef for a number of reasons:
* Increases the fragility of the pipeline and requires a Chef build to
pass on the already large platform matrix times 2.
* AngryChef builds will not be required in our new Buildkite based
pipeline as Chef is not used to manage the underlying instances in the
elastic queues.
We just built/promoted AngryChef 15.0.293 out of band and will continue
to do this if future AngryChef builds are required.
Signed-off-by: Seth Chisamore <schisamo@chef.io>
|
|\
| |
| | |
Enable angrychef again, but disable hab builds
|
|/
|
|
|
|
| |
Hab builds failing prevents rubygems from promoting right now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Add missing items from the chef-14 branch
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Take angrychef out of the expeditor config
|
| |
| |
| |
| |
| |
| |
| |
| | |
Angrychef 15.0.293 never built so we can't properly promote chef right
now and we're in a half released state. This hopefully gets us out of
it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Rename the windows_dfs :install actions to :create
|
|/
|
|
|
|
| |
We're creating these dfs shares so it makes a lot more sense to make the action create. This is probably what people using Chef would expect.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| |
| |
| | |
MsysTechnologiesllc/VSingh/bootstrap-session-timeout
Chef 15: Add --session-timeout bootstrap option for both ssh & winrm
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We converted --winrm-session-timeout MINUTES
to --session-timeout SECONDS
If someone is providing a short session timeout, it's possible
that they're doing so based on the flag accepting minutes. We'll warn
them and suggest an alternative so that if things go wrong,
they'll know where to start looking.
We can remove this once we remove the deprecation for
winrm-session-timeout
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
We added default value for session-timeout, but the tests
weren't aware of that because config was mocked.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit f652cbfd532042620565c6464c2a9cef947f3b0d.
Timeouts are the right way to go, but we need to update the tests
to account for the defaulted values.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| |
| |
| | |
- Updated deprecated flag to MINUTES.
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Add bootstrap option --session-timeout.
- Add wirnrm-session to deprecations.
- Default --session-timeout value is 60 secs(same was added for --winrm-session-timeout).
- Modify existing specs related to old winrm session timeout key and add specs for session timeout.
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|