Make worker data available so a worker's status can be determined before being safely deregistered

[susanpann]

Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your feature request, making sure it's handled appropriately.

Prerequisites

• I have searched open and closed issues to make sure it isn't already requested
• I have discussed this in #feature-discussion or #backlog and the consensus is that this is something we plan on adding in the near future
• I have written a descriptive issue title
• I have linked the original source of this feature request
• I have labelled the value stream (area/core, area/steps, ...)
• I have added the kind/enhancement label

The enhancement

Make worker data available so a worker's status can be determined before being safely deregistered.

What is the problem this solves or benefit it gives

While thinking about creating basic scaling capability, it was found that there's no nice way of determining whether a worker machine is in use prior to deregistering it. Currently, the delete worker API is called and watches for an error message that the worker can't be deleted.

Proposed solution

Workarounds

Links

Internal Discussion: https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1659913751164329

[mjhilton]

This feature is under consideration for implementation in the next 3 months.

[octoreleasebot]

Release Note: Created new api worker task lease endpoint

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.2	2024.2.5816
2024.3+	all releases