Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unable to change chef_environment #163

Closed
mike10010100 opened this issue Aug 8, 2018 · 4 comments
Closed

Unable to change chef_environment #163

mike10010100 opened this issue Aug 8, 2018 · 4 comments

Comments

@mike10010100
Copy link

I'd like to be able to change my chef_environment for Dokken, but am currently unable to do so.

How it works using other test kitchen provisioners: https://docwhat.org/setting-environment-test-kitchen

@espoelstra
Copy link

@mike10010100 see #162 where I've asked about the same. It turns out you CAN set those things in your .kitchen.yml under the provisioner block and it will pass them through to the correct spot.

See this .kitchen.yml from a cookbook I just added Dokken to instead of the crazy Vagrant setup that required a lot of host side configs and installs.

@mike10010100
Copy link
Author

mike10010100 commented Aug 9, 2018

@espoelstra Ah, perfect, it's able to see the environment now, but oddly I'm unable to get Dokken to recognize my example node:

provisioner:
  name: dokken
  always_update_cookbooks: true
  nodes_path: test/integration/nodes
  environments_path: test/environments
  client_rb:
    environment: kitchen

Does the nodes_path section work with Dokken?

@espoelstra
Copy link

I believe it sets the node attributes automatically, I'm not sure if it supports passing them in as I didn't need to supply any node information in my testing.

@espoelstra
Copy link

See also #129

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants