-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{SQL} Fixing failing test for log replay #17672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{SQL} Fixing failing test for log replay #17672
Conversation
|
SQL |
…kic/fixing_test_records
…/fixing_test_records
|
Fix for the issue - #17603 |
| 'storage_sas': 'sp=rl&st=2021-04-12T13:07:20Z&se=2021-04-30T21:07:20Z&spr=https&sv=2020-02-10&sr=c&sig=igoGWjvYceuSkuHRzkm6oPPxitRlSYgGvmdwTbr7WTM%3D', | ||
| 'storage_uri': 'https://mibrkicstorage.blob.core.windows.net/mibrkicportal', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exposing sas token for your storage account has security issue.
Could you create a storage account (using StorageAccountPreparer) and generate sas token on demand?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can try, but the thing is that I will need to publish file to storage account as well. With powershell I had a lot of problems doing that. Hope it will not be the case 🤞
working This reverts commit 8a5c5ce.
Description
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.