Adding the option of passing custom --build-arg(s)…

[steview]

to docker buildx via Bash functions

[rwadstein]

Can you give an example of how this would have been used?

[AlexCoplandSage]

Sorry to revive an old PR but I've come across a situation where passing custom build-args seems to be required.

We've built a shared package for accessing SBC and are currently hosting this on the GoProposal Github account. To install this we need to add a fine grained read-only token for composer so it can access the repo. We're in the process of getting the token added to the pipeline environment variables but we're currently stuck getting the token into the docker build.

We had some success adding the token as a deployment variable and installing the package within entrypoint.sh, but this feels like the wrong side to perform the installation. As far as I understand if we pass the token as a --build-arg and clean up after composer has pulled the package the token shouldn't remain within the image.

Have we missed something obvious here or is the a better way to do things?

[noodl]

Does this replacement still work if there are multiple build arg? This test suggests not..

$ var='foo bar wibble bar'
$ echo ${var/bar/meep}
foo meep wibble bar