Problem
cloudlist's per-provider config supports services: as a positive allowlist, but there's no way to express "enumerate everything except X".
To drop a single service from a provider's default set today, you have to manually list every other supported service. That's tedious and brittle — any time cloudlist adds a new service for that provider, every config that used the workaround needs updating to keep the new service enumerated.
cloudlist already has this pattern for other filter dimensions: exclude_account_ids for AWS and exclude_project_ids for GCP. Services are the only filter dimension where the exclude form is missing.
Solution
Add exclude_services as a first-class option that mirrors how services works today.
YAML:
- provider: gcp
exclude_services:
- cloud-function
project_ids:
- my-projectCLI:
cloudlist -p gcp --exclude-service cloud-function
Resolution semantics:
- Start from
services: if set (intersected with the provider's allowed set), otherwise default to all supported services for that provider.
- Drop any entries listed in
exclude_services.
- Unknown values in either list are silently dropped (matching the existing
services: behavior — typos shouldn't fail the whole run).
Backward compatible: the new field is additive, existing services: semantics unchanged.
Problem
cloudlist's per-provider config supports
services:as a positive allowlist, but there's no way to express "enumerate everything except X".To drop a single service from a provider's default set today, you have to manually list every other supported service. That's tedious and brittle — any time cloudlist adds a new service for that provider, every config that used the workaround needs updating to keep the new service enumerated.
cloudlist already has this pattern for other filter dimensions:
exclude_account_idsfor AWS andexclude_project_idsfor GCP. Services are the only filter dimension where the exclude form is missing.Solution
Add
exclude_servicesas a first-class option that mirrors howservicesworks today.YAML:
CLI:
Resolution semantics:
services:if set (intersected with the provider's allowed set), otherwise default to all supported services for that provider.exclude_services.services:behavior — typos shouldn't fail the whole run).Backward compatible: the new field is additive, existing
services:semantics unchanged.