Skip to content

cub run prune-configmaps

cub run prune-configmaps

For each group of immutable v1/ConfigMap resources sharing a confighub.com/ResourceNameStableCore annotation, retains at most the configured number of newest (highest confighub.com/RevisionNum) entries, removing the rest. The newest entry retains the confighub.com/RenderRevision: Latest annotation; older retained entries have it stripped and are marked with confighub.com/VisitorOptions: IgnoreProvided. Mutable ConfigMaps are left untouched. Mutating. Supported toolchains: Kubernetes/YAML

cub run prune-configmaps [flags]

Options

  -h, --help                         help for prune-configmaps
      --revision-history-limit int   Maximum number of immutable ConfigMaps with the same ResourceNameStableCore annotation to retain. Older versions beyond the limit are removed. Defaults to 10.

Options inherited from parent commands

      --change-desc string      change description
      --changeset string        changeset to associate units with
      --clearance stringArray   class of guarded reason this change is cleared for, as KEY, KEY=VALUE[,VALUE...], KEY!=VALUE[,VALUE...], or !KEY to refuse any path carrying KEY (repeatable). A guarded path this does not cover is not written, and the withheld change is reported as a conflict
      --context string          The context to use for this command
      --debug                   Debug output
      --dry-run                 dry run mode: execute functions but skip updating configuration data
      --executor-space string   Space ID or slug whose executor to use for builtin functions (org-level only)
      --filter string           filter to apply (slug, space/filter, or UUID)
  -o, --output string           Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
      --protect                 record the paths this change writes as protected local overrides, so a later merge from upstream does not overwrite them; by default a change claims nothing and each path keeps the protection it already has
      --quiet                   No output
      --resource-type string    resource-type filter
      --show string             Select which part of the function response to display. One of: output, values, data
      --space string            space ID to perform command on
      --toolchain string        Toolchain type for the function invocations (default "Kubernetes/YAML")
      --unit strings            target specific units by slug or UUID (can be repeated or comma-separated)
      --wait                    wait for completion
      --where string            where filter
      --where-data string       where data filter
      --where-resource string   filter which resources the function operates on
      --worker string           worker to execute the function

SEE ALSO