Open happz opened 1 year ago
Hi @happz !
Thanks for creating the issue!
I hope this is the last TF option we need to implement manually... Actually, that's why we've introduced tf_extra_params
...;) But I agree would be easy to do and can simplify this.
(As discussed internally, we can't decide this value automatically. Maybe use a default constructed from the project's URL, but this info is already sent with the payload so it can be used on the TF part.)
Since there is a workaround and it's a one-time action, I don't promise anything but we can guide you to implement that if you want to speed this up.
What's needed:
Oh, and an idea. We can enforce this for people using internal TF, WDYT? (edit: On the other hand, we can't easily check that it's the correct one..;)
Still relevant but not high priority. If someone wants to give it a look we can help.
Description
As of now, the following is needed to propagate an optional business unit tag to Testing Farm, to tag provisioning resources for better accounting granularity:
Can Packit add a key for this value, and take care of propagating it to Testing Farm?
Benefit
Importance
Not a blocker, but the current option looks way too much like a workaround.
What is the impacted category (job)?
Testing Farm tests, General
Workaround
Participation