Gregg Tanzillo

@kbrock I thought you fixed this one?

To be honest, I'm not familiar with the issue that the "legacy report" check was meant to address. I do recall that in the distant past we had an issue...

cc @bdunne

@kbrock and I looked at config/settings.yml. As an experiment, we did the following: ```ruby orig=YAML.load_file("./config/settings.yml") File.write("./config/settings2.yml", YAML.dump(orig)) s2=YAML.load_file("./config/settings2.yml") s3=JSON.parse(s2.to_json, :symbolize_names => true) File.write("./config/settings3.yml", YAML.dump(s3)) ``` ```diff (git:kasparov) ~/work/ibm/manageiq$ diff -wb...

API usage: ``` http://localhost:3000/api/vms/10000000000775?attributes=last_compliance_conditions,last_compliance_condition_expressions Response: { "href": "http://localhost:3000/api/vms/10000000000775", "id": "10000000000775", "vendor": "openstack", "format": null, "version": null, "name": "te-2wqc-tnefkpuld6b5-o7cx47e2jeuo-server-qpad26atkfb4", "description": null, "location": "unknown", "config_xml": null, "autostart": null, "host_id": null, "last_sync_on": "2019-06-13T12:27:32Z",...

@chessbyte I guess it belongs with https://github.com/ManageIQ/manageiq-api/issues/782, which was completed. Should I create a new epic or add it to that one and open it up again? Also, this is...

@lpichler Can you take a look at this one?

/cc @bdunne

@NickLaMuro What do you want to do with this one?