Compute attributes crate and update API actions don't validate the attributes. It blindly accepts and saves any hash. That can easily lead to storing wrong values without any feedback for users. Such compute attribute can later break UI forms and cause undefined behavior in the provisioning process.

The same validations should be performed on host create API: http://projects.theforeman.org/issues/3649

Expected behavior:
The API actions must check keys and values of compute attributes and return meaningful error messages.

Currently the keys and values differ quite a lot across the providers. http://projects.theforeman.org/issues/21580/ normalizes them for the read actions. Validations should accept the same keys and values and be consistent with the normalized output.