hey anybody got a sample plugin to fill docker image tags de

Question

hey anybody got a sample plugin to fill docker image tags depending on environment variables at hand

enough-analyst-54434 · Answer

I think the feature you need is built in See the Tagging Images docs here <https www pantsbuild org v2 10 docs tagging docker images|https www pantsbuild org v2 10 docs tagging docker images>

happy-kitchen-89482 · Answer

Hi There are some examples here <https www pantsbuild org docs tagging docker images using env vars to include dynamic data in tags>

happy-kitchen-89482 · Answer

Unfortunately it looks like the <https github com pantsbuild example docker|Docker example repo> doesn t have examples of this

happy-kitchen-89482 · Answer

< curved television 6568> when you return something to add perhaps

bitter-orange-16997 · Answer

well right now the setup that works for me is with environment variables and mix of semver and pre release plus a build number

bitter-orange-16997 · Answer

says `1 0 1 buildargs PRE RELEASE BUILD `

bitter-orange-16997 · Answer

which gives `1 0 1 dev 1234` on develop and `1 0 1` on main

bitter-orange-16997 · Answer

the whole issue is developper experience

happy-kitchen-89482 · Answer

Ah then I m not understanding the question Can you explain a little more about what the feature you d like is and how it s different from the built in ability to tag via an env var

bitter-orange-16997 · Answer

so currently we use `1 0 1 buildargs PRE RELEASE BUILD ` as mentionned

bitter-orange-16997 · Answer

to be precise ` buildargs COMPONENT X VERSION buildargs PRE RELEASE BUILD `

bitter-orange-16997 · Answer

we have a script that will populate `PRE RELEASE BUILD` as needed depending on the branch

bitter-orange-16997 · Answer

but for all of this to work we use a script that performs the branch build mapping and we d like that logic to be transparent

bitter-orange-16997 · Answer

because right now this forces use to populate the environment before running any pants command

happy-kitchen-89482 · Answer

What is `buildargs`

bitter-orange-16997 · Answer

sorry I meant `build args` as explained <https www pantsbuild org docs tagging docker images using env vars to include dynamic data in tags|here>

happy-kitchen-89482 · Answer

Oh I see sorry I thought this was some in house construct Right makes sense

happy-kitchen-89482 · Answer

So you want a plugin to compute the value of `PRE RELEASE BUILD` instead of having to set it outside of Pants

bitter-orange-16997 · Answer

exactly yes

bitter-orange-16997 · Answer

or basically any pointer to something similar

bitter-orange-16997 · Answer

it looks like something similar is fairly straight forward for Python packages but I haven t had much success with Docker images

curved-television-6568 · Answer

What I ve done is to source a ci vars sh file from the pants bootstrap script That way it is transparent both in dev and on ci pipeline run

bitter-orange-16997 · Answer

that idea crossed my mind but thought I d go for a cleaner approach

bitter-orange-16997 · Answer

I think I ll do that as well unless I find a better way along the way

bitter-orange-16997 · Answer

thanks

curved-television-6568 · Answer

If you find a cleaner way please share

happy-kitchen-89482 · Answer

A cleaner way might involve adding a plugin hook there

happy-kitchen-89482 · Answer

But TBH modifying the pants script seems pretty clean to me

happy-kitchen-89482 · Answer

You just have to remember to copy over the updates if you update ` pants`

happy-kitchen-89482 · Answer

We could add an env var setting hook in the standard ` pants`

happy-kitchen-89482 · Answer

< bitter orange 16997> that script lives in if you want to send a pull request

happy-kitchen-89482 · Answer

So that future adopters of Pants can enjoy your work slightly smiling face

hundreds-father-404 · Answer

A concern I have there is it makes it harder to consume updates to the ` pants` script you have to deal with merge conflicts now Not the end of the world and seems viable for Benoit to work around this today but I m curious how else we could solve this before we memorialize changing ` pants` script

bitter-orange-16997 · Answer

well yes another issue is that that sort of versioning scheme affects all artifacts published in most projects they follow a similar scheme perhaps Docker images less so than other artifacts and an ideal solution would integrate easily with all artifacts including those handled by plugins

bitter-orange-16997 · Answer

but well this is good enough for now

happy-kitchen-89482 · Answer

We can add a hook into ` pants` that brings in env vars from a sidecar script if it exists

curved-television-6568 · Answer

<https pantsbuild slack com archives C046T6T9U p1646062690280559 thread ts=1646062109 130599 amp cid=C046T6T9U> Good idea Will look into it slightly smiling face

curved-television-6568 · Answer

< happy kitchen 89482>