Missing support for credential_process

[albertomurillo]

minio-go can obtain credentials from a configured aws config file.

This process, however, only looks for static credentials and does not support the credential_process mechanism to execute an external program that obtains the required credentials.

This is useful in environments where federated authentication is in place and long-living credentials are forbidden.

[harshavardhana]

Will take a look @albertomurillo

[albertomurillo]

Will take a look @albertomurillo

I have a patch for this... I am preparing the PR

[V3ckt0r]

hey @harshavardhana and @albertomurillo,

Does this minio library support source_profile in aws config files. Such an example being:

aws config

[pod_role]
web_identity_token_file = /var/run/secrets/eks.amazonaws.com/serviceaccount/token
role_arn = <arn_a>

[assume_role]
source_profile = pod_role
role_arn = <arn_b>
role_session_name = <something>

Env vars

AWS_CONFIG_FILE=<path-to-config-file>
AWS_ROLE_ARN=<arn_a>
AWS_WEB_IDENTITY_TOKEN_FILE=/var/run/secrets/eks.amazonaws.com/serviceaccount/token
AWS_DEFAULT_REGION=us-west-2
AWS_PROFILE=assume_role
AWS_REGION=us-west-2

I saw PR #1486, but I don't think this fixes it. Please confirm?

I was trying to replicate what is described here with the library