Disable Scopes

[ryanmelt]

What is the use case or problem this feature would solve?

Some scopes are only needed in bursts and waste resources when unused.

Describe the solution you'd like

Add a toggle to the Admin Scopes page to disable a scope.
This would stop all scope microservices.

Additional context

No response

Screenshots

No response

[crawlchat]

Thanks for the request! Here's some context that's relevant:

Related existing functionality

COSMOS already has Microservice Control (added in v6.2.0) — in the Admin Microservices tab, you can Stop, Start, and Restart individual microservices, and there are also "Stop All" / "Restart All" bulk buttons when a service filter is applied .

The Admin Scopes tab currently supports scope-wide toggles like Command Authority and Critical Commanding, but does not currently have a toggle to disable/stop all microservices belonging to a scope .

Gap vs. this request

• The Microservices tab lets you filter and bulk-stop, but that filtering isn't scoped to "all services in Scope X" from the Scopes tab itself.
• There's no persisted "disabled" flag on a scope that would prevent its microservices from being (re)started automatically (e.g., on system restart or plugin reload).

To help an engineer scope this properly, could you clarify:

1. Should "disable" just stop currently running microservices for that scope, or should it also prevent them from auto-starting again (e.g., after a system restart)?
2. Should this apply to all microservices tied to the scope (including built-in ones like DECOM, CVT, etc.) or only user/plugin-installed microservices?

This will help determine if this is a straightforward addition to the existing Microservices bulk-stop feature (filtered by scope) or requires a new scope-level "enabled" flag with broader implications.