Project

General

Profile

Actions

Bug #12824

closed

In directive, change input for parameter from technique editor from text to textarea

Added by Matthew Frost over 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Medium
Priority:
56
Name check:
Fix check:
Regression:

Description

Hello Rudder,

Let me start by saying amazing project what you are doing!

I have some feedback over the directives page of rudder currently I am trying to abstract data away from techniques and one thing I am creating is a technique to deploy certificates and add them to correct groups but I have noticed that the text field in directives is not multi-line.

So my question is would it be possible to make the text entry field in directives multi-line like that same text box in ensure file contents in the technique editor?

Thank you!!!


Subtasks 1 (0 open1 closed)

Bug #13752: Change "Common" Technique directives.st files to support multiline parametersReleasedNicolas CHARLESActions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #12825: Adding a parameter to an existing technique in technique editor without updating directives leads to unexpanded variable nameResolvedFrançois ARMANDActions
Actions #1

Updated by Alexis Mousset about 6 years ago

  • Category set to Web - Config management
  • Target version set to 4.3.4
Actions #2

Updated by Benoît PECCATTE about 6 years ago

  • Target version changed from 4.3.4 to 4.3.5
Actions #3

Updated by François ARMAND about 6 years ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Effort required set to Small
  • Priority changed from 0 to 88

OK, so real long term correction is to be able to select the kind of field generated by the technique parameter.

The short term solution is to just use textarea in place of input text.

Actions #4

Updated by François ARMAND about 6 years ago

  • Related to Bug #12825: Adding a parameter to an existing technique in technique editor without updating directives leads to unexpanded variable name added
Actions #5

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.3.5 to 4.3.6
  • Priority changed from 88 to 87
Actions #6

Updated by François ARMAND almost 6 years ago

  • Subject changed from Directives Textbox to In directive, change input for parameter from technique editor from text to textarea

I'm not sure why I set it to "critical".

So, we should change the generated metadata to "textarea".
As that input is given to a cfengine bundle/dsc method parameter, we need to verify that:
- line returns are correctly quoted,
- big, long texts are not truncated / badly quoted.

Actions #7

Updated by François ARMAND almost 6 years ago

  • Assignee set to Vincent MEMBRÉ
Actions #8

Updated by Vincent MEMBRÉ almost 6 years ago

  • Effort required changed from Small to Medium
  • Priority changed from 87 to 56

This appear to be nastier to change.

I changed to a textarea field, but the string is formatted to be correctly indented with the promiser in the ruder-directives.cf file

If we use set this string:

Small text
multiline
to check

the rudder-directives.cf corresponding call is:

      "Global configuration for all nodes/test" usebundle => test("Small text
      multiline
      to check");

Adding spaces on the left of multiline and "to check" line

Actions #9

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from New to In progress
Actions #10

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2052
Actions #11

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from Pending technical review to Pending release
Actions #12

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.6 and 5.0.2 which were released today.
Changelog
Changelog
Actions

Also available in: Atom PDF