added environ credentials support for YDB

[asmyasnikov]

Supported environ credentials for YDB using parameter use_env_credentials in connection string.

Example with access token credentails:

export YDB_ACCESS_TOKEN_CREDENTIALS="my-secret-token"
goose ydb "grpcs://localhost:2135/local?use_env_credentials&go_query_mode=scripting&go_fake_tx=scripting&go_query_bind=declare,numeric" status

Example with yandex cloud service account key file credentials:

asmyasnikov@asmyasnikov-ox goose % YDB_SERVICE_ACCOUNT_KEY_FILE_CREDENTIALS=/Users/asmyasnikov/sa.key go run ./cmd/goose ydb "grpcs://ydb.serverless.yandexcloud.net:2135/ru-central1/b1ggoeimp4lontjmo81g/etn8p4ne5m3v7a5at514?us
e_env_credentials&go_query_mode=scripting&go_fake_tx=scripting&go_query_bind=declare,numeric" -dir testdata/ydb up
2025/11/26 14:08:29 OK   20251126110810_00002_add_column_password_hash_into_table_users.sql (232.8ms)
2025/11/26 14:08:29 goose: successfully migrated database to version: 20251126110810
asmyasnikov@asmyasnikov-ox goose % YDB_SERVICE_ACCOUNT_KEY_FILE_CREDENTIALS=/Users/asmyasnikov/sa.key go run ./cmd/goose ydb "grpcs://ydb.serverless.yandexcloud.net:2135/ru-central1/b1ggoeimp4lontjmo81g/etn8p4ne5m3v7a5at514?us
e_env_credentials&go_query_mode=scripting&go_fake_tx=scripting&go_query_bind=declare,numeric" -dir testdata/ydb down
2025/11/26 14:08:43 OK   20251126110810_00002_add_column_password_hash_into_table_users.sql (285.17ms)
asmyasnikov@asmyasnikov-ox goose % YDB_SERVICE_ACCOUNT_KEY_FILE_CREDENTIALS=/Users/asmyasnikov/sa.key go run ./cmd/goose ydb "grpcs://ydb.serverless.yandexcloud.net:2135/ru-central1/b1ggoeimp4lontjmo81g/etn8p4ne5m3v7a5at514?us
e_env_credentials&go_query_mode=scripting&go_fake_tx=scripting&go_query_bind=declare,numeric" -dir testdata/ydb up
2025/11/26 14:09:05 OK   20251126110810_00002_add_column_password_hash_into_table_users.sql (274.85ms)
2025/11/26 14:09:05 goose: successfully migrated database to version: 20251126110810
asmyasnikov@asmyasnikov-ox goose % YDB_SERVICE_ACCOUNT_KEY_FILE_CREDENTIALS=/Users/asmyasnikov/sa.key go run ./cmd/goose ydb "grpcs://ydb.serverless.yandexcloud.net:2135/ru-central1/b1ggoeimp4lontjmo81g/etn8p4ne5m3v7a5at514?us
e_env_credentials&go_query_mode=scripting&go_fake_tx=scripting&go_query_bind=declare,numeric" -dir testdata/ydb status
2025/11/26 14:09:09     Applied At                  Migration
2025/11/26 14:09:09     =======================================
2025/11/26 14:09:09     Wed Nov 26 14:07:21 2025 -- 20240112115229_00001_create_first_table.sql
2025/11/26 14:09:10     Wed Nov 26 14:09:05 2025 -- 20251126110810_00002_add_column_password_hash_into_table_users.sql

[asmyasnikov]

@mfridman can you consider this enhancement?

[mfridman]

Sure, happy to take a look. Seems reasonable.

[mfridman]

I think you need to run go mod tidy, the go.sum doesn't seem right.

[asmyasnikov]

go mod tidy clear =/

asmyasnikov@asmyasnikov-ox goose % rm -f go.sum
asmyasnikov@asmyasnikov-ox goose % go mod tidy
asmyasnikov@asmyasnikov-ox goose % git status
Current branch: master
This branch corresponds to "origin/master".

there is nothing to commit (use the "-u" option to show untraceable files)

[mfridman]

Wow, now that I'm thinking about it, this is why I didn't want to merge this. This adds an insane amount of entries to the go modules file and it's not something I want to maintain long-term.

In the upcoming /v4 version I'm going to split goose as a library from the CLI code, so they will have different go.mod. I.e., the deps required to build the goose binary are separate from the actual goose provider code.

Curious, is YDB using google cloud apis, or google apis just for the "common types" (e.g., here's a slimmed down version of googleapis https://buf.build/googleapis/googleapis)

[mfridman]

Unless this is a bug in Go, I've never seen it add that many entries. 🤔

[asmyasnikov]

Yes, YDB use google cloud apis only for the "common types" (duration, any, decriptor, empty, timestamp)

But fortunately googleapis doesn't make breaking changes. Never in my memory

[asmyasnikov]

@mfridman CI broken because latest commits in github.com/mfridman/tparse incompatible:

Run go install github.com/mfridman/tparse@main
  go install github.com/mfridman/tparse@main
  shell: /usr/bin/bash -e {0}
  env:
    GOTOOLCHAIN: local
go: downloading github.com/mfridman/tparse v0.18.1-0.20251127013823-841410793c3d
go: github.com/mfridman/tparse@main: github.com/mfridman/[email protected] requires go >= 1.25.0 (running go 1.24.10; GOTOOLCHAIN=local)
Error: Process completed with exit code 1.

[asmyasnikov]

@mfridman Whats a plan for this PR? Wait v4?