You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I noticed that while AWS credentials can be injected via env vars (AWS_SECRET_ACCESS_KEYAWS_ACCESS_KEY_ID) for azure, credentials are only taken from environment for tests and making use of env vars for actual usage is missing ( AZURE_STORAGE_ACCOUNTAZURE_STORAGE_ACCESS_KEY).
Is there a reason to avoid using AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_ACCESS_KEY env vars for azure? I find way more convenient using environment vars for credentials instead of adding them to the json config file.
IMHO using env vars can ease sharing config while keeping a low exposure for credentials, delegating variable injection to tooling focused on credentials management.
The text was updated successfully, but these errors were encountered:
@AlbertoGarciaFdez The AWS credentials feature is provided by AWS SDK not Aptly. The Azure blob Go SDK (https://github.com/Azure/azure-storage-blob-go) we depend on does not provide such functionalities. At the time Azure publish was implemented, that was the only option available. The latest Azure blob SDK supports the feature you want, but it requires Go 1.8 while Aptly right now wants to be compatible with Go 1.5. You will likely get the feature automatically in the future after the Go version and blob SDK are updated in Aply.
Hi, I noticed that while AWS credentials can be injected via env vars (
AWS_SECRET_ACCESS_KEY
AWS_ACCESS_KEY_ID
) for azure, credentials are only taken from environment for tests and making use of env vars for actual usage is missing (AZURE_STORAGE_ACCOUNT
AZURE_STORAGE_ACCESS_KEY
).Is there a reason to avoid using
AZURE_STORAGE_ACCOUNT
andAZURE_STORAGE_ACCESS_KEY
env vars for azure? I find way more convenient using environment vars for credentials instead of adding them to the json config file.IMHO using env vars can ease sharing config while keeping a low exposure for credentials, delegating variable injection to tooling focused on credentials management.
The text was updated successfully, but these errors were encountered: