source "https://rubygems.org"

gem "omnibus", github: ENV.fetch("OMNIBUS_GITHUB_REPO", "chef/omnibus"), branch: ENV.fetch("OMNIBUS_GITHUB_BRANCH", "main")
gem "omnibus-software", github: ENV.fetch("OMNIBUS_SOFTWARE_GITHUB_REPO", "chef/omnibus-software"), branch: ENV.fetch("OMNIBUS_SOFTWARE_GITHUB_BRANCH", "main")
gem "artifactory"

gem "ffi", ">= 1.9.14", "!= 1.13.0"

# Pinning to 2.4.0 as 2.6.0 version breaks the Windows build
# Ref: https://buildkite.com/chef/inspec-inspec-main-omnibus-release/builds/815#018a1db4-2971-4e77-8bca-32d058fe8c12/173-340
# We can try reverting this change once it gets fixed in the omnibus-toolchain as per slack conversation
gem "ffi-yajl", "= 2.4.0"

# This development group is installed by default when you run `bundle install`,
# but if you are using Omnibus in a CI-based infrastructure, you do not need
# the Test Kitchen-based build lab. You can skip these unnecessary dependencies
# by running `bundle config set --local without development` to speed up build times.
group :development do
  # Use Berkshelf for resolving cookbook dependencies
  gem "berkshelf", ">= 7.0"

  # Use Test Kitchen with Vagrant for converging the build environment
  gem "kitchen-vagrant", ">= 1.3.1"
  gem "test-kitchen", ">= 1.23"
  gem "winrm-fs", "~> 1.0"
end