Project

General

Profile

Bug #2218

Smart Class Parameter: Override for specific host does not work, if using type JSON

Added by Florian Sachs over 8 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

System Setup
Foreman Host: RedHat 6.3
Database: Postgresql 9.2
Puppet: puppet-3.1.0
PuppetDB on same host, same Postgresql Cluster, but different Database
Foreman installed via yum-Repository: foreman-1.1stable-1.el6.noarch

Our Linux Server Environment uses Puppet with Foreman acting as ENC. Whenever possible, the parameters used, should be set in Foreman as Smart Class Parameters.
We often use JSON Data, to provide structured data to our puppet classes.

When using type JSON, I found following behaviour:
  • I can paste my JSON data to the field "default value" and it gets saved.
  • When reopening the class, the JSON Data is displayed with whitespave removed (which is actually ok)
  • I cannot use add a new matcher values <<-- VERY BAD
When using type STRING, the i found following behaviour:
  • I can paste my JSON data to the field "default value" and it gets saved.
  • When reopening the class, the JSON Data is displayed as I pasted it (the Linefeeds etc are displayed correctly)
  • I can add new matcher values
  • When reopening the class, the JSON Data of the matcher values is displayed as I pasted it (the Linefeeds etc are displayed correctly)
  • When trying to switch from type STRING to JSON, and save the class, nothing happens

As everything works, when I use the STRING type, I will do so, but I think, the behaviour should be consistent.

History

#1 Updated by Anonymous over 4 years ago

  • Description updated (diff)
  • Status changed from New to Resolved

should be OK by now

Also available in: Atom PDF