ydb - Mirror of YDB github repos

	Commit message (Collapse)	Author	Age	Files	Lines
*	YQL-20095: Enable readability-simplify-boolean-expr	vitya-smirnov	2026-05-07	1	-9/+2
\| \| \| \|	commit_hash:b3d7609795f9aeaaafe9cb65dbb2c6460582a4ec
*	support cloud auth for CREATE EXTERNAL DATA SOURCE (yql part)	yumkam7	2026-03-23	1	-0/+5
\| \| \| \| \| \| \| \| \| \| \| \| \|	structured token will require service_account_id and resource_id and AUTH_METHOD=IAM will require SERVICE_ACCOUNT_ID and INITIAL_TOKEN_SECRET[_NAME\|_PATH] Initial token is used on EDS creation for resolving resource_id/cloud_id and verifying database access, then service_account_id and resource_id will be used for delegated token issue (about same as used for async replication) commit_hash:3eec95e2dea61654a1939bd92549222f752d9654
*	KIKIMR-24294: Add new (*_PATH) settings for secrets in SQL commands	yurikiselev	2025-11-27	1	-0/+208
	Secrets are being reworked in YDB. Previously, they were used in async replication, transfer, and external dat source commands via settings like `..._NAME`. The new secrets will work with the new settings (for more details, see [here](https://nda.ya.ru/t/jqkP2-PX7NLLWp "title")). Here, we add their support when parsing the corresponding SQL commands. 1. Add new secrets paired settings with the `..._PATH` prefix to all old settings. 2. Add parameter usage checks: they must be used in a mutually exclusive manner, meaning that only old settings or only new ones can be used in one SQL command. 3. Add TablePathPrefix pragma values to the new parameter values, since the new settings name schema objects. commit_hash:d7db87d3b07e1b3ccf8981b241f0489db3506924