Teardown · asset_service

← cluster alinma_int asset_service teardown

Teardown — asset_service

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

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

Cannot teardown: other apps depend on objects being removed:
  - insights.assets_sink (app: insights) depends on asset_service.assets_dm
  - insights.benchmark_values_by_asset_sink (app: insights) depends on asset_service.benchmark_constituents_ft, asset_service.benchmarks_dm
  - search.items_mv (app: search) depends on asset_service.assets_dm
  - alinma_bff.report_allocation_daily_mv (app: alinma-bff) depends on asset_service.taxonomy_nodes_dm
  - alinma_bff.book_of_business_accounts_mv (app: alinma-bff) depends on asset_service.currencies_dm
  - alinma_bff.marketplace_assets_mv (app: alinma-bff) depends on asset_service.assets_dm
  - alinma_bff.report_holdings_daily_mv (app: alinma-bff) depends on asset_service.assets_dm
  - alinma_bff.book_of_business_party_clients_mv (app: alinma-bff) depends on asset_service.currencies_dm
  - alinma_bff.book_of_business_portfolios_mv (app: alinma-bff) depends on asset_service.currencies_dm
  - alinma_bff.book_of_business_clients_mv (app: alinma-bff) depends on asset_service.currencies_dm
  - … and 27 more

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

Tear down together: [alinma-bff, asset_service, insights, opportunity, 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: asset_service

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