-
Notifications
You must be signed in to change notification settings - Fork 51
simianfacter/Facter 4 issue #61
Comments
Closing, more recent commits could have resolved this. |
Recent commits have not fixed this, and the existing code fails with an error (that gets swallowed and therefore isn't visible on stdout...) related to argparse. This cannot be what you're using internally... anyway, my version is here. Would a PR be good? |
Can you provide traceback? You can run it directly "/usr/local/bin/simianfacter -j"
of course, but your version can't output json(current default). |
Hey @maximermilov, $ sudo /usr/local/munki/simian/bin/python src/simian/util/simianfacter -j
Traceback (most recent call last):
File "simianfacter_from_", line 114, in <module>
main()
File "src/simian/util/simianfacter", line 92, in main
help='output JSON')
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/argparse.py", line 1294, in add_argument
action = action_class(**kwargs)
TypeError: __init__() got an unexpected keyword argument 'type' Pardon that I'm not sure why it needs to output json... my issue trying to integrate any version past 2.4.x last year was that my custom site fact wasn't being picked up. I see it in the json output, but it's not integrated into the |
Seems you have local modification to the script, because |
😅 Well that was an errant issue that maybe was never in any checkout, but even with that exact file it's definitely something else amiss that's causing a whole bunch of values to be dropped in https://github.com/google/simian/blob/8675db57c78abf7cbbd254e3ff0aa47a1d8134ea/src/simian/mac/client/flight_common.py#L411-L522
notice simiantrack and configtrack are populated. When I switch in master's version of simianfacter, I get |
What creates |
Immediate traceback with cfacter and simianfacter the moment it hits the new structured fact output:
I'm working on a PR, just submitting this in case someone beats me to it with how y'all solved this internally... 😉
The text was updated successfully, but these errors were encountered: