Project

General

Profile

Actions

Refactor #9836

closed

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

Added by Tomáš Strachota about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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 open1 closed)

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

Also available in: Atom PDF