Jason Burden

Is it possible to leverage a .kitchen.yml attribute for this? ohai should set it in production, but I think you should also be able to supply the hostname via attribute...

In your suites: section you'd want to set an attribute value for "hostname: 'my.host.name" As shown in the documentation: https://docs.chef.io/workstation/config_yml_kitchen/ ```suites: - name: suite_name run_list: - recipe[cookbook_name::recipe_name] attributes: { foo:...

Hmm, that's true, it's probably a system attribute that would get over-written/ridden anyway. 🤔 This may not be feasible unless there's some way to "spoof" the system hostname.

Another option and might be easier is to set "tags" on the system that define what the system is. I'm assuming you're using the Hostname to make some logic decisions...

@ncalteen We use a tool called Gossamer to setup sessions where we create a "session" for this and then you specify that "profile" in your .kitchen.yml to use that on...

This appears to be working in my local environment. I need to double check my passwords and usernames in the dev environment where it's failing.

Leveraging the rkerberos gem on my dev environment master server, it appears to be functioning as expected when passing the proper credentials: ``` irb(main):001:0> require 'rkerberos' => true irb(main):002:0> krb5...

Local environment still working. Though if un/pw aren't getting set & used properly I could see how it would work locally as it's just using blank values.