[08:30:41] <brouberol>	 Hi y'all! I'd like to delete some images we've published that we don't need anymore. Is https://wikitech.wikimedia.org/wiki/Docker-registry#Deleting_images still up-to-date?
[08:31:40] <brouberol>	 also, unrelated question. Can we define args in blubber that we can reuse in the YAML struct? Something like `arg: {python_version: '3.10.5'}` ?
[08:34:53] <elukey>	 brouberol: o/ it is, but sadly it is not going to do much other than removing some metadata, see https://phabricator.wikimedia.org/T375645
[08:35:28] <elukey>	 you can go ahead and execute it, hopefully we'll be able to clean up stuff once we'll have a way to garbage collect
[08:35:44] <elukey>	 *ahem* review of my proposal *ahem*
[08:37:55] <elukey>	 for the latter, what do you have in mind? In theory if you want to pass args to the docker cmq/entrypoint if you can (even from yaml/helm), but inside the docker image you'll need to add code/configs to handle the parameter
[08:38:03] <elukey>	 (not sure if I got the question correctly though)
[08:42:25] <brouberol>	 re tags: thanks, all done
[08:43:20] <brouberol>	 re args: It's easier to show. https://gitlab.wikimedia.org/repos/data-engineering/airflow/-/merge_requests/29/diffs In that PR, I'd like to define the python version I'm installing with pyenv once, and perform string interpolation of the variable in the blubberfile
[08:43:55] <brouberol>	 kind of like the following in a Dockerfile:
[08:43:55] <brouberol>	 ARG PYTHON_VERSION=3.10.5
[08:43:55] <brouberol>	 RUN pyenv install ${PYTHON_VERSION} && pyenv global ${PYTHON_VERSION}
[09:07:20] <elukey>	 in theory if you have PYTHON_VERSION=3.10.5 right after line 45 (among the env variables), you should be able to use it like ${PYTHON_VERSION} when you run commands. In theory those should be commands executed with the custom environment set up in the config
[09:07:25] <elukey>	 have you tried ?
[09:14:43] <brouberol>	 I haven't, but I think you're right! It's just that I had ARG vs ENV in mind, but injecting the PYTHON_VERSION in the env of the build stage is a good idea 
[09:14:44] <brouberol>	 thanks!
[09:25:31] <elukey>	 not exactly 100% configurable as you wanted but it is a start :)
[09:27:32] <brouberol>	 indeed
[09:28:09] <brouberol>	 also FYI, I tried the following but the interpolation does not seem to work. Not a big deal, I just thought I'd share
[09:28:09] <brouberol>	 environment:
[09:28:09] <brouberol>	 PYENV_ROOT: /tmp/pyenv
[09:28:09] <brouberol>	 PYTHON_VERSION: 3.10.5
[09:28:09] <brouberol>	 PYTHON_SITE_PACKAGES: "${PYENV_ROOT}/versions/${PYTYHON_VERSION}/lib/python3.10/site-packages"
[09:36:47] <akosiaris>	 if you need some support for a feature in blubber, we can ask to be added btw. WMF owns and writes the software.
[09:44:37] <brouberol>	 +1, let me think about how to formalize it, but support for the equivalent of docker ARG and composable environment would be nice!
[13:29:30] <cdanis>	 brouberol: feel free to chat with dduvall 
[13:29:46] <brouberol>	 ack thanks