refactor!: rename hydrovu source to pvacd_hydrovu for multi-tenant layout (ST2DAT-241)

[crawson-icasa]

Why

• BernCo is the first case of two agencies on one source system. The single HydroVu tenant was called hydrovu, so the platform name and the tenant name were the same string. There was no room for a second tenant beside it. docs/sources/bernco_hydrovu.md catalogued the blockers in its Open Question 1.

How

• Tenant-scoped names become pvacd_hydrovu. Platform-scoped names stay hydrovu.
• Moved: the config block, the registry entry, the source folder, the dataset, and the job and schedule names. Assets are now raw_pvacd_hydrovu_readings, canonical_bundles_pvacd_hydrovu, and frost_load_pvacd_hydrovu. The deploy variable SECRET_HYDROVU becomes SECRET_PVACD_HYDROVU, so BernCo's ticket adds a second export rather than reworking this one.

Notes

• BREAKING CHANGE: raw_pvacd is superseded by raw_pvacd_hydrovu, and the transform watermark moves with it. PVACD's dlt cursors reset on the first run after deploy.
• No objects were copied. raw_pvacd/ is left in place, orphaned.
• BernCo still needs a SECRET_BERNCO_HYDROVU export and a secretmanager.secretAccessor grant on hydrovu_bernco. This was a rename only, so its ticket decides whether to extract the shared HydroVu client or copy it.

[github-actions]

Your pull request is automatically being deployed to Dagster Cloud.

Location	Status	Link	Updated
aqueduct_dagster_defs_definitions		View in Cloud	Aug 29, 2026 at 02:04 AM (UTC)

[likithabommasani21]

Looks good to me
Note : The FROST clean-out needs to happen before the renamed pipeline's first run against production, not after — otherwise there's a window where the old data and the fresh re-post coexist and you get duplicates anyway. Just want to make sure that's sequenced correctly.