Remove Databricks v1 provider in favor of v2
Offen
- Vorherrschende Sprache
- Rust
- Sterne
- 54.2k
- Forks
- 6.2k
- Ø Merge
- 3 T. 2 Std.
- Gemergte PRs (30 T.)
- 262
Beschreibung
**What problem would this solve?**
Databricks providers sometimes show both v1 and v2 options confusing users which to choose
**What would a good outcome look like?**
Only Databricks v2 remains
**Possible approaches**
We can remove the databricks v1 provider and implement a shim to route config files which were pointed at databricks to v1 to upgrade the config file provider entry to v2
**Additional context**
N/A
- [x] I have verified this does not duplicate an existing feature request
Do not begin implementation until the issue reaches **Ready** on the [Goose Issues board](https://github.com/orgs/aaif-goose/projects/1).
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.