Change Server/Database in Data Gateway Data Source

The whole gateway/data source implementation needs a re-work:

1. Reports published to the service should not rely on the server/database combination to identify a data source to use. That match should be done as part of the publishing process and a Data Source name (or key in the background preferably) should be picked. Once on the service, the reports/datasets should rely on that key so the name or properties of the datasource can change without breaking the report.
2. Data source admins should have the ability to see a list of objects affected by changes to the DS. I know this is possible with PowerShell, but it requires O365 Admin role. It should be available to PowerBI Admins. Having a report in the service that can be fired from the datasource properties (lineage) would also be helpful and it can be built based on the existing API.
3. Data sources list should be paged and searchable so large implementations can still be managed.

Ultimately it seems MS is looking more into the VNet setup than keeping the gateway. If that can handle security seamlessly then all this gateway work will eventually be discarded. It would be nice to know where they are going.

We're planning to move a database; the lineage shows 469 impacted child items (semantic models, dataflows, datamarts) in 39 workspaces. This should be a simple data source update however the way Power BI handles data sources is unlike any other enterprise reporting application. We have to manually republish and update every single item. The original idea was posted in 2019 and five years later we still don't have a mechanism to easily update data sources when migrating databases.