Hi what would be the way to use env variable for generating

Question

Hi what would be the way to use env variable for generating docker repository name During our CI CD on AWS we fetch the region and the account id to push the image to different deployment env staging production ECR repository So it can t be a static name <https www pantsbuild org docs tagging docker images setting a repository name>

curved-television-6568 · Answer

If you go with a `build arg` you can provide the value for that arg as an ENV variable

curved-television-6568 · Answer

Does that make sense to you otherwise I can elaborate wink

refined-addition-53644 · Answer

yeah I was guessing that would be the case It s just setting all these build arg means I need to set them everywhere i e even locally Otherwise pants will complain I guess I should write a plugin where I check for the `build arg` specific ENV variable and use default values when running locally Do you think it s possible to do that using plugin for `docker image`

refined-addition-53644 · Answer

I am talking about this suggestion for adding extra tags <https www pantsbuild org docs tagging docker images providing additional image tags with a plugin> Can this be modified to read these env vars passed using `build arg`

curved-television-6568 · Answer

The tags plugin example will only be able to provide custom tags not affect the build args or repository name

curved-television-6568 · Answer

for posterity at least a few months this test case may be illustrative of using build args in tandem with env vars to customize the repository name <https github com pantsbuild pants blob 11b4fd412631c6315b474e49fe482dec1767cf29 src python pants backend docker goals package image test py L607 L622|https github com pantsbuild pants blob 11b4fd412631c6315b474e49fe482dec1767cf29 src python pants backend docker goals package image test py L 22>

curved-television-6568 · Answer

gt It s just setting all these build arg means I need to set them everywhere i e even locally Otherwise pants will complain yea well using a bootstrap script this may not be as painful as it sounds ``` pants bootstrap $ CUSTOM REPO = local ``` <https github com pantsbuild setup blob db310991388e3903b8b1356ed1a4e8747adfc925 pants L20>

curved-television-6568 · Answer

sorry pasted wrong link at first

curved-television-6568 · Answer

with that bootstrap script in place you can have the ENV var automatically populated for all local devs while when provided by the CI system will take precedence when running the pipeline

refined-addition-53644 · Answer

ok thanks Will give this a try