chef-config 18.0.185 → 18.1.29

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 02d7be6f393115be22791e12784d1acdb83a7eb559dac797f150b282c51276b4
-  data.tar.gz: 0f99238f554cffe14d183b3a31936fd602855fd36fed0a527b2df07322ec9001
+  metadata.gz: c488c053032691185a6abb6f89ee7402bb4f96c6e2cbedc078b68884f132dbd6
+  data.tar.gz: 9f124dff47af67e561fd98ae61304061038d8e446adf421d8f4e9abce3a21218
 SHA512:
-  metadata.gz: 9b3188ab117d3be06e0358b23051fa1723e641eaa402dc05650bc07f12c601034801d817e11ed6525aa396904604e494f7fc8916dcfb44def0a9c976773b9ecc
-  data.tar.gz: b75e3cd2caf5d33818940628a74fee4f51b78a9d0b7e9dd5e40f7e59a22f299608ca8a802ae1ddc8f4d32478df89bf0576a45daa576590f003984c8b3ed591d8
+  metadata.gz: 8949292663a9ea3f8da676043022d16d9a87e6ec027d981215ed248bdc2ecb8b88686cef5ee194df6e99c4f03c0c73c5ce37d9c5e416beb028429ecaf56b6689
+  data.tar.gz: 88dea33ca3826cd1c516588c1f3f0bce07584151913334068c986ff53467060ebb197de3a0ad7777ad82f53ecac0f06e042d032aafb15eac0bef2f72805dd365

data/lib/chef-config/config.rb

@@ -778,6 +778,16 @@ module ChefConfig
     # Then the public key from the new cert is pushed to Chef Server for authentication
     default :migrate_key_to_keystore, false
 
+    # When we move certs into the certstore, we need to manage multi-user scenarios.
+    # This flag is used in conjunction with 'migrate_key_to_keystore'. If 2 users, Bob and Terri, are using
+    # this node, we need a means to separate the private keys of each user. Alternately, if an Admin
+    # configures the node and then relies on a system account to run chef afterward, we need a second
+    # method for that. Setting this in the client.rb file with a "user" flag will cause chef to create
+    # and manage separate private keys. We look for this flag to be set to "user" to manage distinct users keys with,
+    # However, if that key is set to anything else, we assume that keys are to be stored in the LocalMachine store.
+    # Leaving this key omitted has the same effect as setting it to anything other than "user"
+    default :auth_key_registry_type, nil
+
     # When registering the client, should we allow the client key location to
     # be a symlink?  eg: /etc/chef/client.pem -> /etc/chef/prod-client.pem
     # If the path of the key goes through a directory like /tmp this should

data/lib/chef-config/version.rb

@@ -15,5 +15,5 @@
 
 module ChefConfig
   CHEFCONFIG_ROOT = File.expand_path("..", __dir__)
-  VERSION = "18.0.185".freeze
+  VERSION = "18.1.29".freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: chef-config
 version: !ruby/object:Gem::Version
-  version: 18.0.185
+  version: 18.1.29
 platform: ruby
 authors:
 - Adam Jacob
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-11-15 00:00:00.000000000 Z
+date: 2023-03-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: chef-utils
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 18.0.185
+        version: 18.1.29
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 18.0.185
+        version: 18.1.29
 - !ruby/object:Gem::Dependency
   name: mixlib-shellout
   requirement: !ruby/object:Gem::Requirement
@@ -158,7 +158,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.32
+rubygems_version: 3.3.7
 signing_key: 
 specification_version: 4
 summary: Chef Infra's default configuration and config loading library