The CreateQueue API has changed and now requires a new "jobRunAsUser" → "runAs" field in the request (one of two values: QUEUE_CONFIGURED_USER or WORKER_AGENT_USER).
What was the solution? (How)
Updated the test fixtures to pass this new API request field.
What is the impact of this change?
Consumers of deadline-cloud-test-fixtures can now create queues using the new API shape.
How was this change tested?
Tested this with casillas2/deadline-cloud-worker-agent#133 and confirmed that this change uses the new API fields when making CreateQueue requests.
What was the problem/requirement? (What/Why)
The
CreateQueueAPI has changed and now requires a new"jobRunAsUser"→"runAs"field in the request (one of two values:QUEUE_CONFIGURED_USERorWORKER_AGENT_USER).What was the solution? (How)
Updated the test fixtures to pass this new API request field.
What is the impact of this change?
Consumers of
deadline-cloud-test-fixturescan now create queues using the new API shape.How was this change tested?
Tested this with casillas2/deadline-cloud-worker-agent#133 and confirmed that this change uses the new API fields when making
CreateQueuerequests.Was this change documented?
No
Is this a breaking change?
No