Updating the configuration after renaming or deleting a used middleware

[blackneil]

What problem does this solve?

middleware "xxx@file" does not exist

Proposed solution

Updating the configuration after renaming or deleting

Alternatives you've considered

Unlink, rename and link
Unlink and delete

Which area does this relate to?

Middlewares

Additional context

No response

[chr0nzz]

Good catch. Renaming or deleting a middleware left the routes using it pointing at a name that no longer exists, which is where that error comes from.

Fixed and scheduled for the next release. Renaming now moves the routes with it, and deleting one that is still in use is refused and tells you which routes, with the option to remove it from them and delete.

Services, TLS profiles and plugins had the same problem, so those are covered too. No more unlink and relink.

[blackneil]

Thanks ! 👍