Project

General

Profile

Actions

Bug #2686

closed

foreman-config doesn't change boolean settings

Added by Dominic Cleal almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

The foreman-config script since #2343 doesn't change boolean settings:

2.0.0p0 :001 > Setting.find_by_name('signo_sso').value
  Setting Load (0.2ms)  SELECT "settings".* FROM "settings" WHERE "settings"."name" = 'signo_sso' ORDER BY name LIMIT 1
 => false 

$ script/foreman-config -e development -k signo_sso -v true
true

2.0.0p0 :002 > Setting.find_by_name('signo_sso').value
  Setting Load (0.2ms)  SELECT "settings".* FROM "settings" WHERE "settings"."name" = 'signo_sso' ORDER BY name LIMIT 1
 => false 

It appears this is due to the interface change on the setting model, where the controller was updated and not this script, which interacts directly with the model.

(from https://bugzilla.redhat.com/show_bug.cgi?id=976578)


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #2343: app/models/setting.rb#default chokes on nil attributesClosedTomáš Strachota03/20/2013Actions
Actions #1

Updated by Dominic Cleal almost 11 years ago

  • Status changed from Assigned to Ready For Testing
Actions #2

Updated by Dominic Cleal almost 11 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF