Renovate pipe does not support private S3 repositories

[b_lagerweij]

We are using Bitbucket pipelines in combination with a private repository hosted on S3. Although the renovate product supports S3 hosted repositories just fine, it does not work for the pipe. The reason is that the pipe.yaml does not propagate the AWS_ACCESS_KEY_ID and  AWS_SECRET_ACCESS_KEY environment variables.

  - name: AWS_ACCESS_KEY_ID

    default: $AWS_ACCESS_KEY_ID

  - name: AWS_SECRET_ACCESS_KEY

    default: $AWS_SECRET_ACCESS_KEY

  - name: AWS_REGION

    default: $AWS_REGION

  - name: AWS_DEFAULT_REGION

    default: $AWS_DEFAULT_REGION

Could you please update the pipe.yaml file, and add the above lines ?

[Igor Stoyanov]

Hi @b_lagerweij . Thanks for your feature request.

We will think about adding support of pre-execution script, so will have the ability to implement your custom logic before the pipe execution.

We will notify you when this feature will become available.

Regards, Igor

[Ben]

Hi @b_lagerweij 

I am reaching out to the pipes development team for clarity on this.

Cheers!

- Ben (Bitbucket Cloud Support)