summaryrefslogtreecommitdiff
path: root/chef.gemspec
Commit message (Collapse)AuthorAgeFilesLines
* Correcitng linting issue - extra blank line on line 31John McCrae2022-09-261-1/+0
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* Permit ruby 3.0 for AIXMarc A. Paradise2022-09-231-1/+6
| | | | | | | | We have not been able to build ruby 3.1 on AIX at this time. Until we are able to do so, we are leaving chef-18 on Ruby 3.0 for that platform. Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
* Resolve 'lock file is unreadable error' for chef's lockfileNeha Pansare2022-09-221-1/+1
| | | | Signed-off-by: Neha Pansare <neha.pansare@progress.com>
* Update dependencies in lock file for separate windows gemspecNeha Pansare2022-09-221-1/+1
| | | | Signed-off-by: Neha Pansare <neha.pansare@progress.com>
* Maintain separate gemspec for windows, update lock file to include ucrt ↵Neha Pansare2022-09-221-18/+1
| | | | | | block as this is the only way bundle install can pull windows gems, add lock file knife for the same reason Signed-off-by: Neha Pansare <neha.pansare@progress.com>
* Integrate ruby 3.1 into buildsJohn McCrae2022-08-231-4/+21
| | | | | | | | | This is a combination of 64 commits, the originals were mostly repeating one-line messages so that history has not been kept here. Signed-off-by: Thomas Powell <thomas.powell@progress.com> Signed-off-by: Marc Paradise <marc@chef.io> Signed-off-by: John McCrae <john.mccrae@progress.com>
* updating gemspec to overcome fault in unf_extJohn McCrae2022-05-261-0/+1
| | | | Signed-off-by: John McCrae <jmccrae@chf.io>
* Add train-rest as a dep for target modeTim Smith2022-02-241-0/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* net-ftp isn't bundled in Ruby 3.1 anymore so dep on itTim Smith2022-02-071-0/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Relax dep on diff-lcs now that 1.4.0 regression is fixedTim Smith2022-02-041-1/+1
| | | | | | This unblocks all the cucumber deps in test-kitchen Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 18.0 and fix master references18.0Tim Smith2022-01-071-2/+2
| | | | | | Fix more URLs to point to main. Signed-off-by: Tim Smith <tsmith@chef.io>
* add corefoundation gem dependencyrishichawda2021-09-251-0/+1
| | | | Signed-off-by: rishichawda <rishichawda@users.noreply.github.com>
* Add hint on aws-sdk-s3 requirementThomas Heinen2021-09-061-1/+1
| | | | Signed-off-by: Thomas Heinen <theinen@tecracer.de>
* Lowered SDK dependency to check pipeline failuresThomas Heinen2021-09-061-1/+1
| | | | Signed-off-by: Thomas Heinen <theinen@tecracer.de>
* Enable directly using AWS S3 with --recipe-url parameter of Chef ClientThomas Heinen2021-09-061-0/+1
| | | | Signed-off-by: Thomas Heinen <theinen@tecracer.de>
* Add support for secrets stored in HashiCorp VaultMarc A. Paradise2021-08-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Vault secrets are stored as key-value pairs, so the return value from a secret lookup is always a Hash. Example: ``` file "/home/user/test1" do content secret(name: "secret/example", service: :hashi_vault, config: { vault_addr: "vault.example.com", role_name: "example-role" })[:answer] end ``` As shown above, we are expecting a hash from Vault, and are populating the file content based on the value of `:answer` in that hash. Limitations: * This iteration only supports instance authentication via a Vault role connected to an IAM profile. * This iteration does not support versioned secrets Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
* Experimental support for an AWS Secrets FetcherMarc A. Paradise2021-07-141-0/+1
| | | | | | | | | | | | | | | | | In a recipe, usage will look like the following: value = secret(name: "test1", service: :aws_secrets_manager, config: { region: "us-west-1" }) log "My secret is #{value.secret_string}" Note the use of `secret_string` to determine the secret value. The returned object here is Aws::Types::GetSecretValueResponse from the AWS SDK. This beta implementation supports ec2/imds instance profile authentication but also checks standard locations for credentials configuration -- see documentation [1] for a description of default credentials search behavior. [1] https://docs.aws.amazon.com/sdk-for-ruby/v3/api/Aws/SecretsManager/Client.html#initialize-instance_method Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
* Remove knife deps from the chef gemspecTim Smith2021-05-031-17/+8
| | | | | | This should help us slim the size of the install down and it should also greatly speed up testing anything that deps directly on chef. Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove knife exclusions from chef gemMarc A. Paradise2021-04-301-3/+1
| | | | | | | These are no longer required because knife files will no longer be matched by the given pattern. Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
* Move knife to its own gemChef Expeditor2021-03-311-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This moves knife into /knife, in the same way that chef-utils and chef-config are separated. NOTES: == File History == If you see this message as the first message in the history of an knife file, you can see the complete history by using 'git log --follow', 'git config log.follow true' to make it the default behavior in this repository, or 'git config --globa log.follow true' to make it the global default. == API Changes == At the API level, there is one breaking change: CookbookSiteStreamingUploader has been moved out of chef and into knife/core. There were a combination of reasons we chose this path: - CookbookSiteStreamingUploader (CSSU) is only used within Knife. - CookbookSiteStreamingUploader (CSSU) references the command Chef::Knife::CookbookMetadata in order to generate a metadata file for the cookbook to upload - Chef::Knife::CookbookMetadata is no longer available to Chef:: because Knife has been moved to its own gem. Knife gem depends on the Chef gem, so Chef can't depend on something in Knife. A search for usage in related projects (berks, chef-cli) and the Internet at large shows that there are no known external consumers of CSSU. For now, we'll move this class into Knife::Core, as it's going to be faster than splitting off the metadata generation and time is a concern. If we find that we need the metadata generation in chef/ proper, we should evaluate decoupling that functionality from Knife::CookbookMetadata and exposing it via something like `Chef::Cookbook::Metadata#from_cookbook_files` == spec changes == The specs are kept in their existing locations, though we have separated out a `knife_spec_helper` so that we can ensure knife is not directly accessing chef requires; and chef is relying on knife's at all. We also now clear gem paths with each test, to force gem state to reset. This works around a problem where a combination of tests is corrupting the internal Gem state, causing failures in rubygems_spec. See branch `mp/broken-gems` for many more details around findings so far. Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
* ruby 3.0 fixes and post-bundle-install hookLamont Granquist2021-03-181-1/+1
| | | | | | | | | | | | | | | Mostly this is all fixes necessary for ruby 3.0 There's the addition of the appbundle hook which lets us better pull git gems into appbundler Note carefully how after adding the post-bundle-install.rb that trying to pre appbundle-update ohai pulls in chef/chef as bundle installed git gem which fails to install so we go back to only using one appbundle-update on chef/chef and removing the chef/ohai one (which may fix other bugs). Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Update FFI to 1.15.0ffiTim Smith2021-03-061-1/+1
| | | | | | This may fix the issues in 1.14. We'll see. Signed-off-by: Tim Smith <tsmith@chef.io>
* Update our bcrypt_pbkdf dep to allow the final 1.1.0 releasebcrypt_pbkdfTim Smith2021-03-021-1/+1
| | | | | | This should be the same thing except they did a non-RC release. Signed-off-by: Tim Smith <tsmith@chef.io>
* Don't ship dev gems in the shipping artifactLamont Granquist2021-01-201-0/+9
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Updated uuidtools versionKapil Chouhan2021-01-141-1/+1
| | | | Signed-off-by: Kapil Chouhan <kapil.chouhan@msystechnologies.com>
* Pin ffi for now to prevent i386 windows failuresTim Smith2020-12-311-1/+1
| | | | | | ffi 1.14 is not compatible with our i386 windows boxes Signed-off-by: Tim Smith <tsmith@chef.io>
* Add gemspec metadataTim Smith2020-12-311-0/+9
| | | | | | This ensures we have all the links on Rubygems now Signed-off-by: Tim Smith <tsmith@chef.io>
* Update bcrypt_pbkdf to support Ruby 3ruby_3Tim Smith2020-12-301-1/+1
| | | | | | RC2 now includes support for Ruby 3 Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the runtime dep on bundlerTim Smith2020-12-301-4/+0
| | | | | | Bundler is part of Ruby now so it's a waste of time to depsolve for this since it's not possible to have Ruby without bundler 1.10+ anymore. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump Chef Infra to 17bump_17Tim Smith2020-12-181-1/+1
| | | | | | Bump the version to 17 and allow for Ohai 17 Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix for deprecation warningKapil Chouhan2020-12-091-1/+1
| | | | Signed-off-by: Kapil Chouhan <kapil.chouhan@msystechnologies.com>
* Move inspec-core from Gemfile to gemspec for external test script.Pete Higgins2020-12-011-0/+1
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Pull in the new tty-table to unlock new license-acceptancetty-tableTim Smith2020-09-201-1/+1
| | | | | | | | tty-table was holding back a bunch of deps. This will resolve several Ruby 2.7 warnings and lets use use the optimized license-acceptance gem that also had pete's better error handling. This also nukes a few deps to make chef/chef smaller. Includes misc chefstyle fixes for the new version Signed-off-by: Tim Smith <tsmith@chef.io>
* Allow for license-acceptance 2.0 gemTim Smith2020-09-091-1/+1
| | | | | | We're the last place this needed to be bumped Signed-off-by: Tim Smith <tsmith@chef.io>
* Add tty-table & render config listVivek Singh2020-08-241-0/+1
| | | | Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
* require mixlib-shellout 3.1.1+ and pull in new ohaiTim Smith2020-07-221-1/+1
| | | | | | The refactoring to chef-utils requires this new mixlib-shellout. Signed-off-by: Tim Smith <tsmith@chef.io>
* Add comment in gemspecVivek Singh2020-07-211-1/+1
| | | | Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
* Replace highline gem with tty-promptVivek Singh2020-07-211-0/+1
| | | | Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
* Bump Ohai and pin diff-lcsTim Smith2020-06-301-1/+1
| | | | | | diff-lcs 1.4 breaks diff output for us. Pin this for now. Signed-off-by: Tim Smith <tsmith@chef.io>
* Update ffi-libarchive for windows fixes / pin the depTim Smith2020-06-251-1/+1
| | | | | | Make sure we don't later pull in a breaking version here, but make sure we have at least 1.0.3 Signed-off-by: Tim Smith <tsmith@chef.io>
* Allow for the latest net-ssh and ffi 1.13.1Tim Smith2020-06-101-2/+2
| | | | | | | | | | | New net-ssh has several important improvements that our users will probably want: * Support empty lines and comments in known_hosts [donoghuc, #742] * Add sha2-{256,512}-etm@openssh.com MAC algorithms [graaff, #714] * curve25519sha256 support [Florian Wininger ,#690] Signed-off-by: Tim Smith <tsmith@chef.io>
* Test build to see if ffi 1.13.1 worksTim Smith2020-06-091-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Pin FFI to < 1.13 to avoid failures on Windowsexpeditor/inspec-core-bin_4.19.2Tim Smith2020-06-041-1/+1
| | | | | | FFI 1.13 is more strict now and others using it have been abusing it historically on Windows. This results in failures with the new version. We need to let the dust settle before we can use 1.13. Signed-off-by: Tim Smith <tsmith@chef.io>
* try equality pinning to make appbundle-updater happierrhel6Lamont Granquist2020-04-271-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* I believe this is necessary to allow prerelease versionsLamont Granquist2020-04-271-1/+1
| | | | | | | ~> 1.0 does not allow 1.1.0.rc1, while not using the semver operator should. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Require at least train-core 3.2.28 to resolve sudo issuesTim Smith2020-04-131-1/+1
| | | | | | Make sure that even a gem install of chef will work correctly here. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump highline to 2.xlcg/bump-highlineLamont Granquist2020-04-081-1/+1
| | | | | | We need 2.x for ruby 2.7 compat and warning suppresion Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Replace highline.color with pastel.decorateBryan McLellan2020-03-021-0/+1
| | | | | | | | | | Contributes to the removal of the 'heavy' highline dependency (#9359) by switching from highline.color to pastel.decorate, which is a drop-in replacement. Pastel is part of the tty[1] family of libraries. [1] https://github.com/piotrmurach/tty#3-components Signed-off-by: Bryan McLellan <btm@loftninjas.org>
* Add chef-vault as a dep to chefTim Smith2020-02-121-0/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Require Ruby 2.6+Tim Smith2020-01-211-1/+1
| | | | | | | | We support the last 2 releases of Ruby on Chef. Ruby 2.7 is out so we should remove Ruby 2.5 at this point. We'll add Ruby 2.7 testing in the near future. Signed-off-by: Tim Smith <tsmith@chef.io>
View Lorry Controller Status