Skip to content
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

fix: start windows worker service depending on the worker configuration #144

Merged
merged 1 commit into from
Aug 16, 2024

Conversation

YutongLi291
Copy link
Contributor

What was the problem/requirement? (What/Why)

The Posix deadline-worker service started depending on whether the worker configuration had start_service set to True or False, but the WIndows service did not.

What was the solution? (How)

Also make the WIndows service dependent on the worker configuration in specifying whether the service should start after the install.

What is the impact of this change?

Better and more consistent testing experience across Windows and Posix

How was this change tested?

hatch run fmt, hatch build

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.

Signed-off-by: Yutong Li <52769999+YutongLi291@users.noreply.github.com>
@YutongLi291 YutongLi291 requested a review from a team as a code owner August 16, 2024 00:47
Copy link

sonarcloud bot commented Aug 16, 2024

@YutongLi291 YutongLi291 changed the title fix: start windows service depending on the worker configuration fix: start windows worker service depending on the worker configuration Aug 16, 2024
@ddneilson ddneilson merged commit 602bd3b into aws-deadline:mainline Aug 16, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants