[14:17:47] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 06cloud-services-team, 10Cloud-VPS: ZuulDevOpsBot user can create but not delete a cluster template - https://phabricator.wikimedia.org/T396932#10947384 (10joanna_borun) p:05Triage→03Medium
[14:52:06] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 06cloud-services-team, 10Cloud-VPS: ZuulDevOpsBot user can create but not delete a cluster template - https://phabricator.wikimedia.org/T396932#10947617 (10bd808)
[14:52:09] <wikibugs>	 10Continuous-Integration-Infrastructure (Zuul upgrade), 13Patch-For-Review: Provision Kubernetes cluster and bastion using OpenTofu and Magnum - https://phabricator.wikimedia.org/T396936#10947616 (10bd808)
[15:18:18] <hashar>	 fun thing, one can now `Depends-On: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1159468`
[15:18:27] <hashar>	 and ... it works out of the box!
[15:38:19] <hashar>	 ansible.builtin.command does not seem to support passing environment variables :]
[15:38:50] <corvus>	 it should... point me where you're trying?
[15:39:24] <hashar>	 well to be fair I haven't tried. I am just ranting while reading the upstream doc at https://docs.ansible.com/ansible/latest/collections/ansible/builtin/command_module.html :)
[15:39:31] <hashar>	 also good morning!
[15:41:02] <corvus>	 good morning!
[15:41:14] <corvus>	 hashar: you should be able to set the environment for a command task with https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_environment.html
[15:41:36] <corvus>	 basically, it's not documented on the command task itself because it's one of the things you can do for any kind of task
[15:41:52] <hashar>	 ahhh of course
[15:43:26] <hashar>	 I am sure I had the trouble last week
[15:43:31] <hashar>	 and I should have read the playbook since
[15:44:14] <hashar>	 I already had an environment section and I simply had to add FORCE_COLOR there https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1159468/37..38/playbooks/quibble/run.yaml
[15:44:16] <hashar>	 success
[15:51:12] <hashar>	 so looks like in an extension I can now properly express it depends on another or several other extensions
[15:51:25] <hashar>	 eg CirrusSearch depends on Elastica and EventBus (at least)
[15:51:25] * hashar https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CirrusSearch/+/1163804/4/.zuul.yaml
[15:51:48] <hashar>	 (the zuul PLEASE FIX blue message can be dismissed, it is because I did not add EventBus in the tenant configuration)
[15:53:46] <hashar>	 and our Quibble test software does recognizes the Zuul legacy vars that are injected as environment variable
[15:54:24] <hashar>	 it fails though https://zuul-dev.wmcloud.org/t/wikimedia/build/d99562c2421f48fcbedf8a83f5dac003/console
[15:54:40] <hashar>	 but that is due to lack of recursivity when resolving the dependencies, something we wanted to get rid of
[15:54:52] <hashar>	 krinkle did file a task to stop doing recursive resolution
[15:55:08] <hashar>	 anyway Zuul works