Azure / Azure/azure-kusto-microhack
Installation errors
- Dominant language
- No language data
- Stars
- 42
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
The script deploy.sh downloads two files which are mandatory to complete the badge.
But it fails during the download second of the file:
failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason GET https://adxmicrohacksa.blob.core.windows.net/logistics-telemetry-data-july-22
--------------------------------------------------------------------------------
RESPONSE 403: 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
ERROR CODE: AuthenticationFailed
--------------------------------------------------------------------------------
AuthenticationFailedServer failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
RequestId:cc1439f1-701e-0059-1e54-8228aa000000
Time:2025-02-18T22:26:23.1010127ZSignature not valid in the specified time frame: Start [Tue, 02 Aug 2022 13:54:43 GMT] - Expiry [Fri, 02 Aug 2024 21:54:43 GMT] - Current [Tue, 18 Feb 2025 22:26:23 GMT]
--------------------------------------------------------------------------------
.
ERROR DETAILS: https://aka.ms/AzCopyError/AuthenticationFailed
Failed to perform copy operation.
3. Configuration completed
Link to the file itself
https://adxmicrohacksa.blob.core.windows.net/logistics-telemetry-data-july-22?sp=rl&st=2022-08-02T13:54:43Z&se=2024-08-02T21:54:43Z&spr=https&sv=2021-06-08&sr=c&sig=VjcLSN6vylf%2BfvsB5WiDFhNUuT514YPiDHfWaMl9PgQ%3D
you will find the original link in deploy.sh script
Contributor guide
No contributing guide indexed for this repository
Research direction
Open deploy.sh and inspect the second file download, comparing its Azure Blob URL with the expired link shown in the issue. Run the installation script after the URL is corrected and confirm both mandatory files download successfully and configuration completes without the authentication error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, shell
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100