Add storage location and notification subscription API - #77
Merged
Merged
Conversation
Amp-Thread-ID: https://ampcode.com/threads/T-01a0f838-2233-701d-9912-13798be93e4f Co-authored-by: Amp <amp@ampcode.com>
|
The latest Buf updates on your PR. Results from workflow Lint Protobuf / buf (pull_request).
|
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
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.
Separate storage management from AutomationService into StorageLocationService and storage_location.proto.
Add typed provider references, location rename, SNS/Pub/Sub/Event Grid subscriptions, and location-scoped event history with descending pagination and triggered job/automation IDs. Azure delivery secrets are returned only on creation. StorageLocation.reference remains optional for legacy automation requests; CreateStorageLocationRequest requires it.
Compatibility notes:
Validation: Buf 1.73.0 format, lint, and build pass; git diff --check passes. Core clients were regenerated and tested locally.
Rollout: merge and publish this API first. Core dependency updates and its PR will follow only after publication is confirmed. No Core PR or deployment is included here.