Make artifact repository priority configurable via environment variable

[vaibhavdaren]

Problem

The artifact plugin currently sets a hardcoded high priority for shared artifact repositories (e.g. brew/koji). While useful in some cases, this can:

• Mask packages from system or other repos
• Break workflows that require testing updates, downgrades, or different NVRs
• Force users into workarounds (manual repo edits, disabling repos)

Community feedback suggests repo priority should be configurable, not fixed.

---

Proposal

Introduce an environment variable to override artifact repo priority:

• TMT_ARTIFACT_REPO_PRIORITY

  • If set, overrides the default priority (e.g. 50)
  • If unset, keeps the current behavior (no breaking changes)

This preserves existing defaults while allowing flexibility for advanced and generic integrations (e.g. Testing Farm API).

---

Acceptance Criteria

• Env var overrides artifact repo priority
• Unset env var retains current behavior

[kkaarreell]

I would rather propose to configure it through the test plan itself, e.g.

prepare:
 - how: artifact
   provide:
      - koji.build:123456
      - koji.task:654321
      - koji.nvr:openssl-3.2.6-2.fc42
   repository:
      filepath: /etc/yum.repos.d/myrepo.repo
      id: myrepo
      priority: 110
      enabled: 0 /false
      gpgcheck: 0 /false

[happz]

This should be backed by a genuine plugin key, which would give us an environment variable "for free", see https://tmt.readthedocs.io/en/stable/overview.html#plugin-variables

[kkaarreell]

This should be backed by a genuine plugin key, which would give us an environment variable "for free", see https://tmt.readthedocs.io/en/stable/overview.html#plugin-variables

What if I have two or more how: artifact steps in my tmt plan?

[happz]

This should be backed by a genuine plugin key, which would give us an environment variable "for free", see https://tmt.readthedocs.io/en/stable/overview.html#plugin-variables

What if I have two or more how: artifact steps in my tmt plan?

If you set their "priority" key to different values, tmt has several options: pick the first one, pick the last one, ignore them all, or raise and error and ask you to make up your mind.

Personally, I would vote for the last option, but that probably wouldn't be accepted :)

Edit: one more, create new repo with different priority for each phase, and squash those with same priority into same repositories.