Project

General

Profile

Actions
Copy link

Refactor #9836

closed

Using provider_friendly_name in paths to compute resource related assets can cause problems

Added by Tomáš Strachota almost 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Tomáš Strachota
Category:
Compute resources
Target version:
1.8.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/2247
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Provider friendly names can contain spaces and may vary according to the provider distribution. Therefore they are not suitable for usage for building paths to asset files. We currently use it in the following helpers:

provider_partial_exist?
provider_partial
nic_info_js

provider_friendly_name should be replaced with provider to avoid future complications.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #9824: Unable to show or edit VMWare Compute resourceClosedTomáš Strachota03/19/2015Actions
Actions
Copy link
 #1

Updated by Dominic Cleal almost 10 years ago

  • Related to Bug #9824: Unable to show or edit VMWare Compute resource added
Actions
Copy link
 #2

Updated by Tomáš Strachota almost 10 years ago

  • Status changed from New to Assigned
  • Assignee set to Tomáš Strachota
Actions
Copy link
 #3

Updated by The Foreman Bot almost 10 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2247 added
  • Pull request deleted ()
Actions
Copy link
 #4

Updated by Anonymous almost 10 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Dominic Cleal almost 10 years ago

  • Translation missing: en.field_release set to 28
Actions
Copy link

Also available in: Atom PDF