ubuntu-docker-images team mailing list archive

[Sergio Durigan Junior <sergio.durigan@xxxxxxxxxxxxx>]

On Monday, April 19 2021, Paride Legovini wrote:

> Sergio Durigan Junior wrote on 19/04/2021:
>> Hey Paride, everybody,
>>
>> I'd like to follow up on what we (Paride and I) have discussed post-TGIF
>> today.
>>
>> Basically, I wanted to talk to Paride so that we could come up with a
>> good way to pass credentials around when running the test scripts on
>> Jenkins.  Because the new tests will require us to run some of the
>> scripts from the "utils" repository, and because these scripts require
>> credentials in order to obtain their data from the registries, we will
>> need to handle that.
>>
>> We already have the readonly credentials from AWS (both for the "ubuntu"
>> and the "lts" namespaces), and they will need to be stored in a file
>> called ~/.aws/credentials.  Paride said he wanted to store them in a
>> separate file and then tell the aws program to use it, but unfortunately
>> that doesn't seem to be possible.
>
> Hi Sergio,

Hey Paride,

> Do you have a pointer to what's the blocker on having separate files?
> It seems to me that setting the AWS_CONFIG_FILE and
> AWS_SHARED_CREDENTIALS_FILE env variables should make aws-cli use
> different files for the config/creds. Of course that may not be enough
> in our case, but I'm not sure of what piece is missing...

Ah!  Sorry, I hadn't seen the AWS_SHARED_CREDENTIALS_FILE variable.
Then I stand corrected: it seems to be possible to specify a different
credentials file indeed.  That's good news!

> (I was hoping that setting those env vars alone would have done the trick!)
>
> BTW: should we move this discussion to the new OCI mailing list?

Yes!  Added the list now, thanks!

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14