Project

General

Profile

Actions

Bug #22751

closed

Adding override values doesn't work with 1.17

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

Status:
Closed
Priority:
Normal
Category:
Smart variables
Difficulty:
Triaged:
Team Backlog:
Fixed in Releases:
Found in Releases:
In Kanboard:

Description

The api docs for override values has changed in the foreman 1.17 and wrongly document expected types for 'value' and 'default_value' parameters. This results in hammer interpreting the type as a list and passing all the values in arrays.

Unfortunately this happens at multiple places in the api. Since the proper fix includes some tuning on hammer-cli side as well as adding a custom validator to the api and this issue blocks some other PRs that require 1.17 api exports, I propose to do a temporary fix on hammer side. The proper fix can be delivered later.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #22753: Some API parameters are wrongly documented as enum typesClosedTomáš Strachota03/02/2018Actions
Actions #1

Updated by The Foreman Bot almost 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Tomáš Strachota
  • Pull request https://github.com/theforeman/hammer-cli-foreman/pull/357 added
Actions #2

Updated by Tomáš Strachota almost 7 years ago

  • Related to Bug #22753: Some API parameters are wrongly documented as enum types added
Actions #3

Updated by Martin Bacovsky almost 7 years ago

  • Translation missing: en.field_release set to 342
Actions #4

Updated by Anonymous almost 7 years ago

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

Also available in: Atom PDF