Skip to content

feat: Add a hook to manage PCI device capabilities - #2584

Merged
cardoe merged 2 commits into
mainfrom
pci-device-hook
Oct 26, 2026
Merged

cardoe merged 2 commits into
mainfrom
pci-device-hook

Conversation

@stevekeay

Copy link
Copy Markdown
Contributor

This is similar to the ironic built-in pci-device hook except that it prefixes the capability names, which allows it to clean up old
capabilities. Also, this looks for PCI device data in inventory,
whereas the ironic hook looks for it in plugin_data.

What does this change do?

Upgrade impact

  • This change requires operator action to upgrade. If checked, add the
    upgrade-impact label and a release note: run scriv create from the
    repository root and describe the required action in the generated
    changelog.d/ file. See RELEASING.md.

Operator action means anything a deployment has to do beyond a normal resync:
deploy repo or values changes, new or removed secrets, enabling or disabling a
component, or a manual one-time step.

This is similar to the ironic built-in pci-device hook except that it
prefixes the capability names, which allows it to clean up old
capabilities.   Also, this looks for PCI device data in inventory,
whereas the ironic hook looks for it in plugin_data.
@github-actions

github-actions Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Python test results

824 tests   824 ✅  10s ⏱️
  1 suites    0 💤
  1 files      0 ❌

Results for commit 39688ab.

♻️ This comment has been updated with latest results.

@stevekeay stevekeay changed the title Add a hook to manage PCI device capabilities feat: Add a hook to manage PCI device capabilities Oct 26, 2026
@cardoe
cardoe added this pull request to the merge queue Oct 26, 2026
Merged via the queue into main with commit 4a8be51 Oct 26, 2026
70 of 71 checks passed
@cardoe
cardoe deleted the pci-device-hook branch October 26, 2026 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants