The Jobs feature should enforce schema similarly across all interfaces (UI/ReST/ORM?)

[jmcgill298]

Environment

• Python version: 3.8
• Nautobot version: 1.0.2

Steps to Reproduce

1. Create a Job with field constraints
2. Take any necessary steps to have job in Web/Worker instances
3. Fill out form and notice that the form will not submit until data complies with defined constraints per field
4. Make ReST API call to the job with incorrect data and see that non-compliant data did not prevent the job from being sent to the worker

Expected Behavior

I expected to have a 400 Error and the job not be sent to the worker

Observed Behavior

The job was sent to the worker and the job failed due to invalid data.

[jmcgill298]

Where the description states specifically that this is related to individual field type data, I should also point out that this also goes for the required-ness of the fields. It is also acceptable using the REST interface to not send fields that are required per the Job Field specification.

Another to point out is that Fields that define a default value do not have that default value supplied via the REST interface. The default does not actually act like a default, but just a pre-filled form entry.

In regards to this point, there should be some consideration as to what the data arg should do for non-required fields. It would be a convenience to developers to have all non-required and non-supplied fields default to None; this is the current behavior in the UI.

[glennmatthews]

Most likely this will be addressed by adding an appropriate implementation of validate() and/or validate_data() on the JobInputSerializer class.