In https://github.com/aws-deadline/deadline-cloud-test-fixtures/pull/96 we added functionality to specify and use AWS_ENDPOINT_URL_DEADLINE to set a custom endpoint url. We do not currently set this env variable on the workers so that it can connect to designated endpoint
What was the solution? (How)
Added the following to the worker configuration:
If the environment variable is specified, then add it to the Worker before installation so that it connects to the intended endpoint/farm location.
What is the impact of this change?
Enables AWS_ENDPOINT_URL_DEADLINE usage for the Worker Agent.
How was this change tested?
Setting AWS_ENDPOINT_URL_DEADLINE and running hatch run integ-test i confirmed that the worker would connect to various endpoints.
Was this change documented?
no
Is this a breaking change?
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
What was the problem/requirement? (What/Why)
In https://github.com/aws-deadline/deadline-cloud-test-fixtures/pull/96 we added functionality to specify and use
AWS_ENDPOINT_URL_DEADLINE
to set a custom endpoint url. We do not currently set this env variable on the workers so that it can connect to designated endpointWhat was the solution? (How)
Added the following to the worker configuration:
If the environment variable is specified, then add it to the Worker before installation so that it connects to the intended endpoint/farm location.
What is the impact of this change?
Enables AWS_ENDPOINT_URL_DEADLINE usage for the Worker Agent.
How was this change tested?
Setting
AWS_ENDPOINT_URL_DEADLINE
and runninghatch run integ-test
i confirmed that the worker would connect to various endpoints.Was this change documented?
no
Is this a breaking change?
no
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.