You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.
One gotcha is that chef search normally return a list of results, while a terraform data source (as far as I understand) isn't allowed to do that. So that is why I introduced "unique" above, which would mean that a unique result is expected (and an error would be raised otherwise). Without "unique = true" the result would instead contain the list attribute "rows" with all the results.
The text was updated successfully, but these errors were encountered:
msvticket
added a commit
to deniedboarding/terraform-provider-chef
that referenced
this issue
Jun 28, 2018
To easily use data stored on a chef server in terraform would be very useful.
I envision something you would call like this:
data.chef_search.rabbitmq.rabbitmq.default_password
anddata.chef_search.rabbitmq.host
would then be examples of attributes to use.This is similar to how you would use search in a chef recipe:
https://docs.chef.io/chef_search.html#filter-search-results
One gotcha is that chef search normally return a list of results, while a terraform data source (as far as I understand) isn't allowed to do that. So that is why I introduced "unique" above, which would mean that a unique result is expected (and an error would be raised otherwise). Without "unique = true" the result would instead contain the list attribute "rows" with all the results.
The text was updated successfully, but these errors were encountered: