| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
|
|
|
|
| |
Instead of requiring everything that the HashiVault fetcher requires,
infer what we can and explicitly require access key/access key id to
assemble the token.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
| |
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Update all deps to the latest
|
|/
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Update HashiCorp Vault fetcher to support token auth
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Token-based auth is common in automated environments, so this
change adds support for token-based authentication to the Hashi Vault
secret fetcher.
A new configuration item has been added `:auth_method`, which must be
one of `:iam_role` or `:token`. When `auth_method` is not specified, it
defaults to `:iam_role` for backward compatibility with the initial
implementation.
All authentication methods require a `:vault_addr` configuration entry
If using `auth_method: :token`, a :token configuration entry must also
be provided.
If using `auth_method: :iam_role`, a :role_name configuration entry must
also be provided.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Bump chef-zero to 15.0.9
|
|/
|
|
|
|
| |
This pull request was triggered automatically via Expeditor when chef-zero 15.0.9 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.
|
|\
| |
| | |
Fix tests for new omnibus test systems
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For some reason our temporary AIX 7.2 system does not correctly report
group membership immediately after changes have been made.
Adding a 2 second delay for this platform is enough
to get correct results.
We hope to remove this delay after we get more
permanent AIX 7.2 systems in our CI pipeline.
reference: reference: https://github.com/chef/release-engineering/issues/1617
Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
Some of our new test infrastructure has uids
that are colliding with the 30000 starting point.
Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Bump chef-vault to 4.1.3
|
|/ /
| |
| |
| |
| |
| | |
This pull request was triggered automatically via Expeditor when chef-vault 4.1.3 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.
|
|\ \
| |/
|/| |
ulimit: Fix sensitive property
|
| |
| |
| |
| | |
Signed-off-by: Ashwin <avarma@msystechnologies.com>
|
|/
|
|
|
|
|
| |
- Sensitive property was not working on user_ulimit.
- Added required specs.
Signed-off-by: Ashwin <avarma@msystechnologies.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Disable x25519 until we fix RHEL 7 failures
|
|/
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Bump inspec-core-bin to 4.41.20
|
|/
|
|
|
|
| |
This pull request was triggered automatically via Expeditor when inspec-core-bin 4.41.20 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.
|
|\
| |
| |
| |
| | |
chef/snehal/fix_exception_privilege_is_a_required_property_even_though_its_set
windows_user_privilege.rb : fixed exception: privilege is a required property, even when it was set
|
| |
| |
| |
| | |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Build packages on Intel macOS 12
|
|/ /
| |
| |
| | |
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.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | |
| | |
| | | |
chef/fix-windows-user-account-control-registry-values
windows_uac: fix registry settings for consent_behavior_users
|
| | |
| | |
| | |
| | | |
Signed-off-by: rishichawda <rishichawda@users.noreply.github.com>
|
|\ \ \
| | | |
| | | | |
Fix knife client create
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Jason Barnett <jason.w.barnett@gmail.com>
|
|\ \ \ \
| |_|/ /
|/| | | |
Bump ffi to 1.15.4
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
This pull request was triggered automatically via Expeditor when ffi 1.15.4 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.
|
|\ \ \
| |/ /
|/| | |
bump openssl-1.0.2za
|
| | |
| | |
| | |
| | | |
Signed-off-by: dheerajd-msys <dhsingh@progress.com>
|
|/ /
| |
| |
| | |
Signed-off-by: dheerajd-msys <dhsingh@progress.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|