-
Notifications
You must be signed in to change notification settings - Fork 433
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
Azure: malformed authorization header when authenticating with AZURE_STORAGE_ACCESS_KEY #1322
Comments
Hi! Thanks for reporting this. I think @serprex is our top specialist in Azure. Philip, can you please take a look? |
Yes this seems to work |
So, do we need a pre-release for WAL-G+Azure users? |
@x4m What's blocking rolling a 2.1 release? |
Well, nothing, but do we have features or bug fixes for the release?Frequent releases are great, if we have a stuff for announce.I see there’s ongoing work on MongoDB bin backups support. That’s really cool feature for the release. But it’s not merged yet.--Отправлено из мобильной Яндекс Почты20.08.2022, 01:11, "Philip Dubé" ***@***.***>:
@x4m What's blocking rolling a 2.1 release?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
There's at least support for using managed identity with Azure backend Looking at changes made since May 20th, a few bug fixes like #1292 |
Is there reason that a 2.0.1 patch release isn't an option? This is fairly major imo. |
Great , let’s do a release.--Отправлено из мобильной Яндекс Почты22.08.2022, 19:40, "Daniil Zakhlystov" ***@***.***>:
There's at least support for using managed identity with Azure backend
Looking at changes made since May 20th, a few bug fixes like #1292
Yes, there are also multiple improvements for the Greenplum backups. I guess we can cut a 2.0.1 release.
@x4m what do you think?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
TWIMC, the WAL-G v2.0.1 is now available on the Releases page |
Postgres
Issue description
Describe your problem
After updating from wal-g 1.1 to 2.0 authentication fails with AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_ACCESS_KEY. So wal-g can't access the Azure Storage Account.
Errormessage:
maybe this has something to do with the issue? I'm unsure about that:
https://github.com/wal-g/wal-g/pull/1135/files#diff-0cb36811c5ab07631529c9e82697352bb620d50cf5f88e3e5503bb3e85441caaR261
Please provide steps to reproduce
PGUSER
,PGPASSWORD
,AZURE_STORAGE_ACCOUNT
,AZURE_STORAGE_ACCESS_KEY
,WALG_AZ_PREFIX
,PGHOST
,PGPORT
environment variables/usr/local/bin/wal-g wal-verify integrity timeline --json
Please add config and wal-g stdout/stderr logs for debug purpose
logs
The text was updated successfully, but these errors were encountered: