Repository navigation
Conversation
…url-allow-hosts Do not check Azure disks from the server config against remote_url_allow_hosts Conflicts committed as-is; the next commit resolves them: - src/Disks/DiskObjectStorage/ObjectStorages/AzureBlobStorage/AzureBlobStorageCommon.cpp (both modified) - src/Disks/DiskObjectStorage/ObjectStorages/ObjectStorageFactory.cpp (both modified) - tests/integration/test_allowed_url_from_config/test.py (both modified) - tests/integration/test_merge_tree_azure_blob_storage/test.py (both modified)
Kept the PR's Azure disk host-check, warning and test changes; dropped the unrelated master-only credential-restriction code and tests.
|
Port-AL: cherry-pick conflicts resolved by AI Conflicted files:
Commits:
|
|
@blau-ai resolve conflicts |
# Conflicts: # tests/integration/test_allowed_url_from_config/test.py
|
Conflicts with One file conflicted:
These files merged without conflicts:
Check: after the merge, |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix server startup failure when an Azure Blob Storage disk from the server configuration has an endpoint that is not listed in
remote_url_allow_hosts(since 26.7). Such disks are no longer checked against this list, like S3 disks, also when a data lake table uses one viaSETTINGS disk = .... Disks created bydisk(...)in a query, URLs of table functions and table engines, and redirects are still checked. An existing table on adisk(...)disk whose host is no longer allowed loads with a warning and keeps reading and writing to that host, as for S3 disks; a newdisk(...)with that host is rejected. Closes ClickHouse#124431. (ClickHouse#124721 by @groeneai)Documentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: