Improve dependency handling in service destructor

Created on 22 February 2013, almost 12 years ago

Updated 17 January 2025, 5 days ago

Follow-up of #1891980: Add Service termination API to reliable terminate/shut down services in the container →

Right now, we have no dependency detection during service destruction.

Services that need destruction could depend on each other (e.g. database and databaser key value expirable backend) and we need to make sure that we destruct them in the right order.

Probably requires to extract dependencies, run them through the Graph component and then add them in the right order to the service.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇨🇭Switzerland berdir Switzerland

Live updates comments and jobs are added and updated live.

stale-issue-cleanup

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 5 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024