Discovered via bug: controller_node field present in
project update list but not in detail view
Added tests to assert that "unified" list serializer
produces same fields as the ordinary serializer,
for unified jobs & unified JTs
Added test to check that list serializers do differ
from detail serializer except for allowed differences
Added test to check that list serializers are applied
correctly - only on list views, and that detail views,
likewise, do not use list serializers
Fix the many many bugs discovered by these new
testing mechanisms
Fix bug creating WFJT schedule with passwords:
discard survey_passwords field if given in WFJT
prompts processing method.
Fixed by porting prior JT fix to WFJT method of
same name.
Fix bug where API browser will show encrypted form
of variables in the POST submission box after
failed attempt:
copy extra_data so encrypted data values are not
added in still-linked request.data
Fix a bug where submitted extra_data $encrypted$ string
literal was saved because survey_passwords was empty
when there was no diff from prior.
Allow not answering required password questions with a
non-empty default value when saving a launch config.
The literal $encrypted$ string now gets passed into the
prompts / survey validator.
Translations for dashboard lists -> tooltips
Changing "Portal Mode" to "My View," in part due to translations.
Adding "Job Template" to strings to be translated from OPTIONS on API
Marking translations for JT that has a project that needs to be re-synced.
Marking translations for survey maker
Marking translations for lookup modal directive
Marking translations for empty, "Go To Notifications To Add Template"
Adds strings service for scheduler, and marking strings for translation
Translations for teams linkout from orgs, as well as cred types
Translations for instance groups
Marks translations for the Network UI
Translates strings on the workflow editor
Translations for workflow results
Translations for host event modal and some missing translations on
the stdout page.
* Randomly chose an instance in the controller instance group for which
to control the isolated node run. Note the chosen instance via a job
controller_node field
