-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(api)!: rename jobsRunAs to jobRunAsUser #41
Conversation
807291f
to
075a57a
Compare
058709d
to
8eda08a
Compare
# Use jobRunAsUser if it exists, otherwise jobsRunAs if it exists, otherwise None. | ||
job_run_as_user_data = job_details_data.get( | ||
"jobRunAsUser", job_details_data.get("jobsRunAs", None) | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: should we maybe put a comment like TODO: remove this workaround once service no longer sends jobsRunAs
here too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll be doing a follow-up to remove all jobsRunAs
references once the service swaps (dependent on this), so I should catch this reference.
Signed-off-by: Morgan Epp <[email protected]>
8eda08a
to
4999474
Compare
Signed-off-by: Morgan Epp <[email protected]> Signed-off-by: Graeme McHale <[email protected]>
Signed-off-by: Morgan Epp <[email protected]> Signed-off-by: Graeme McHale <[email protected]>
Signed-off-by: Morgan Epp <[email protected]> Signed-off-by: Graeme McHale <[email protected]> Signed-off-by: Gahyun Suh <[email protected]>
Signed-off-by: Morgan Epp <[email protected]> Signed-off-by: Graeme McHale <[email protected]>
Signed-off-by: Morgan Epp <[email protected]> Signed-off-by: Graeme McHale <[email protected]>
What was the problem/requirement? (What/Why)
The
jobsRunAs
property in the API is being renamed in the service tojobRunAsUser
, so the worker agent needs to follow suit.What was the solution? (How)
The Worker agent uses the following priority order when reading the serivce response:
jobRunAsUser
if it exists in the api response, otherwisejobsRunAs
, otherwiseNone
What is the impact of this change?
Worker Agent works with new API shape.
How was this change tested?
Was this change documented?
N/A
Is this a breaking change?
Yes.