-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support access via symbols #45
Comments
Yes, you are right. There are cookbooks that fail because they use dot notation in the templates for variables that come from search results, so we always have to modify them to use single quotes. |
@justinforce PR and you shall receive. Keeping this open because it's required for feature parity. However, I think with Chef Zero, this repo is gonna end not being heavily maintained. Thoughts, @tobami ? |
actually. closing this as I think I like #42 more as a solution to it if we get around to it. |
I would love to PR, but I left my job and I don't see much DevOps in my future. So long, Chef! We had a good run. I'm very grateful for all the time and test coverage that chef-solo-search netted me. Thanks! |
@michaelglass sorry I missed your question. What Chef Zero will mean for this repo remain to be seen. I don't have any definitive thoughts yet. Are you planning to move to Chef Zero? |
@tobami we've moved to Opsworks |
@michaelglass cool to know, thanks for sharing. Is it working well for you? |
Amazon has great tools but there are a few annoying inconsistencies. alas & alck. |
You should be using a Mash or something that allows access via string index, symbol index, or dot notation. This is the behavior supported by search in Chef. I think the point of this is to work the same way, right?
Thanks!
The text was updated successfully, but these errors were encountered: