Hi there,
Messaging about the latest release of Foreman (1.16). This may also be
pertinent to older versions as well however. (Can't pin it down easily in
the release notes).
I'm currently using Foreman 1.11 and one thing I have is a custom plugin to
interrogate certain custom facts I've written and display them. This
collects application specific data by querying custom facts (that are
structured and contain quite a bit of data) using scoped_search. The issue
I'm getting while testing in 1.16, where structured facts are now broken
down by the new fact importer are;
- It doesn't seem possible to access an entire structured custom fact?
As far as I can see while being imported it's all broken down and stored
directly. An example would be the following below which previously I used
to pull down from the database directly and parse, in addition as the key
names "info1" etc are dynamic can't hardcode to pull out specific values.
{"info1":{"status":"X","time":"Y"},"info2":{"status":"X","time":"Z"},"info3":{"status":"X","time":"Y"},.................}
- The custom facts we have mentioned above can be quite verbose -
meaning that what was previous 3 custom facts is translated to upwards of
35-40, and it's not a great user experience on the UI to view data
together, in many ways it was just easier to look at the json.
I can understand why this change was made for, but was wondering if there
was any way to turn structured fact importing like this off easily? Or if
not if anyone had any ideas how to replicate the previous functionality of
just being able to pull down an entire fact?
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
