Teardown · party — RWM Console

← cluster integration-testing party teardown

Teardown — party

Sinks stop writing immediately. MV state is discarded. Cannot be undone.

Can't tear down party alone — other apps depend on objects being removed:

Cannot teardown: other apps depend on objects being removed:
  - authz.active_party_direct_memberships_mv (app: authz) depends on party.reference_identifiers
  - authz.active_party_memberships_mv (app: authz) depends on party.reference_identifiers
  - authz.active_parties_to_accounts_mv (app: authz) depends on party.customer_relationships
  - authz.team_to_parties_mv (app: authz) depends on party.customer_relationships, party.parties
  - authz.active_parties_to_portfolios_mv (app: authz) depends on party.customer_relationships
  - insights.party_account_via_portfolio_mv (app: insights) depends on party.customer_relationships
  - insights.party_to_account_groups_mv (app: insights) depends on party.customer_relationships, party.parties
  - insights.party_account_direct_mv (app: insights) depends on party.customer_relationships
  - insights.account_groups_mv (app: insights) depends on party.lifecycle_profiles

Include the affected app(s) in the teardown: --app authz --app insights

Tear down together: [authz, insights, party] ▸

2 · Dry-run preview 0 objects · scope = all

Subscriptions (0)

—

Sinks (0)

—

Indexes (0)

—

Materialized views (0)

—

Tables (0)

—

Sources (0)

—

Functions (0)

—

3 · Confirm

Type the app name to confirm expected: party

I understand this is destructive and downstream consumers will lose data.

‹ cancel Blocked — resolve the dependency above to proceed.

RWM Console cluster: risingwave.platform.svc.cluster.local