Dev to Main #348
Merged
Dev to Main #348
Conversation
This file contains 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
…specified, we will specify bucket key as 1234567890 instead.
…-update Private aggregation cloud update -> please run test in Dev Environment
Seburan
added
enhancement
maybellineboon
approved these changes
Jul 1, 2024
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.
Description
Updated Private Aggregation reporting demo to dynamically specify both bucket and cloud environment.
To be able to use this, key and bucket must be specified in the publisher page. sample link: https://privacy-sandbox-demos-news.dev/?key=1234567890&env=aws
From the sample link, this will create an AWS private aggregation report with the bucket key of 1234567890.
Related Issue
NA
Affected services
Other: