Project

General

Profile

Actions
Copy link

Bug #39320

closed

Expose bmc_default_provider setting via v2/features API

Added by Arvind Jangir 2 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Arvind Jangir
Category:
BMC
Target version:
-
Difficulty:
easy
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/smart-proxy/pull/943, https://github.com/theforeman/smart-proxy/pull/946
Fixed in Releases:
Foreman - 3.19.0, Foreman - 5.0.0
Found in Releases:
Red Hat JIRA:

Description

The bmc_default_provider setting is used as a fallback when no bmc_provider param is passed in BMC API requests. Exposing it allows Foreman to discover the configured default provider from the v2/features endpoint.

Actions
Copy link
 #1

Updated by The Foreman Bot 2 months ago

  • Status changed from New to Ready For Testing
Actions
Copy link
 #2

Updated by The Foreman Bot 2 months ago

  • Fixed in Releases 3.20.0 added
Actions
Copy link
 #3

Updated by Anonymous 2 months ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #4

Updated by Ondřej Gajdušek about 2 months ago

  • Fixed in Releases 5.0.0 added
  • Fixed in Releases deleted (3.20.0)
Actions
Copy link
 #5

Updated by The Foreman Bot about 2 months ago

  • Pull request https://github.com/theforeman/smart-proxy/pull/946 added
Actions
Copy link
 #6

Updated by The Foreman Bot about 2 months ago

  • Fixed in Releases 3.19.0 added
Actions
Copy link

Also available in: Atom PDF