Project

General

Profile

Actions
Copy link

Bug #5778

closed

Using json to create directive is not working with API

Added by Vincent MEMBRÉ about 10 years ago. Updated about 10 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
API
Target version:
2.10.8
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

You can't use json to create a directive.

Parameters is a problem ... you have to put a whole string instead of using JSON => really bad ...

And even if you manage to get pass through the parameters

The api awaits for a techniqueName but only reads it as url parameters... so it does not find it in json

using it as parameter will breack the json

need to fix all the things here

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 10 years ago

  • Subject changed from using json to create directive is not working with API to Using json to create directive is not working with API
Actions
Copy link
 #2

Updated by François ARMAND about 10 years ago

  • Status changed from New to In progress
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
Actions
Copy link
 #3

Updated by François ARMAND about 10 years ago

  • Status changed from In progress to Pending technical review
  • Pull Request set to https://github.com/Normation/rudder/pull/702
Actions
Copy link
 #4

Updated by François ARMAND about 10 years ago

  • Assignee changed from François ARMAND to Nicolas CHARLES
Actions
Copy link
 #5

Updated by François ARMAND about 10 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/702 to https://github.com/Normation/rudder/pull/707
Actions
Copy link
 #6

Updated by François ARMAND about 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.8 and 2.11.5, which were released today (16/12/14)

Actions
Copy link

Also available in: Atom PDF