-
Notifications
You must be signed in to change notification settings - Fork 4
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
Public info #14
Public info #14
Conversation
Question to the floor: Where do we want to have our "default" attribute location be for the external IP? Currently it is in public_info.remote_ip, is this sufficient or should we save it in another location as well? |
@RSTJNII public.info.external_ip? Also just a reminder about tags. As Discussed, we can set a tag as "external_ip: 1.1.1.1" as an example |
public_info.remote_ip is already being consumed in customer environments and so I think it should be retained. I don't think having a second attribute, public_info.external_ip, in the same subhash adds value. I opted to leave naming alone, and made the tag RemoteIP to keep things consistent. Tagging is working. Note that the tag is just a string, not a key:value pair.
|
Should be good, but can we get a test? |
This is failing tests. Will resubmit once testing is resolved. |
Cookbook doesn't appear to be in Jenkins, passes on my box:
I added an exception into the recipe if this doesn't run properly as I believe an explicit convergence failure is better than bad data or a failure somewhere where the data is consumed. This also serves as a simple test as if any of the moving parts aren't moving node['public_info'] won't be set leading to a convergence failure during kitchen tests. Rubocop revision was also dropped to a known working revision as RuboCop 0.21 and 0.20 were throwing dependency errors on my box. |
👍 from me. |
Test still passing after master merge:
|
Merge Thomas C's public_info Ohai plugin into rackops_rolebook