Teardown · party — RWM Console

← cluster alinma_qa 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:
  - search.party_holder_edges_mv (app: search) depends on party.customer_relationships
  - search.party_active_relationships_mv (app: search) depends on party.customer_relationships
  - search.party_reference_identifier_terms_mv (app: search) depends on party.reference_identifiers
  - search.active_parties_mv (app: search) depends on party.parties
  - insights.party_account_direct_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_via_portfolio_mv (app: insights) depends on party.customer_relationships
  - insights.account_groups_mv (app: insights) depends on party.lifecycle_profiles
  - alinma_bff.account_primary_client_mv (app: alinma-bff) depends on party.parties, party.reference_identifiers
  - alinma_bff.party_advisor_kpi_recent_customer_users_mv (app: alinma-bff) depends on party.lifecycle_profiles
  - … and 11 more

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

Tear down together: [alinma-bff, authz, insights, party, search] ▸

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-alinma.alinma-rw.svc.cluster.local