feat(destinations): withhold azureblob + gcs from the type enum (ENG-4200) - #396
Merged
Merged
Conversation
…4200) Blob-storage sinks write objects with an uncontrolled object-generated-by-svix prefix, so hold them back from creation until we own the naming. Remove azureblob and gcs from the destination type enum and the type description. The per-field descriptions (account/container/credentials) are left in place so re-adding is a clean revert; the server impl is unchanged. See Linear ENG-4200. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
RajatPawar
force-pushed
the
rajatspawar/eng-4200-withhold-blob-storage
branch
from
August 18, 2026 22:44
2f6fa2a to
3ab5509
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes
azureblobandgcsfrom the destinationtypeenum so the API/SDK no longer offer blob-storage destinations for creation. They write objects with an uncontrolledobject-generated-by-svixprefix, so we're holding them back until we own the naming.The server implementation stays intact — this is only the contract. Per-field descriptions (
account,container,credentials) are intentionally left so re-adding is a clean revert.Part of holding back blob storage — see ENG-4200. Companion removals: docs (amp-labs/docs #695), dashboard (amp-labs/client #2265). Server guard to follow.
🤖 Generated with Claude Code