[pipelines] Provide access to secrets inside Docker builds

[enricopesce]

❓ Customize the docker build phase

I need to implement some environment variables on the DockerAsset stages but these are automatically created by pipelines.

How can I customize these?

Thank you!!

[hoegertn]

Can you elaborate on your use case? What env variables do you need to set?

[enricopesce]

On the Docker build phase I need to pass credentials to PHP composer tool for downloading private dependencies.

Generally I'm looking for a customization of the build phase for passing the build args.

[hoegertn]

Ok I understand, but building assets and so images should happen in the synth phase, shouldn't it?

Otherwise, this is related to #10999

[enricopesce]

yes! another problem is the impossibility to retrieve secrets values on the assets build phase

Usually, I used the CodeBuild spec file with the env sequence, but in this scenario, I don't have control of these DockeAssets CodeBuilìd instances.

Thank you

[rix0rrr]

There is currently no way to do that, sorry.

[github-actions]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[ulyr]

If you need to do this there's a way
you can pass an environment variable to the asset build stage in the pipeline definition and then pass that environment variable onto the actual docker build that's going to build your containers by using build secrets that take their values from the environment.
kind of a hacky, no so straight forward solution but it works.