Project

General

Profile

Bug #9243

Technique "Enforce a file content" breaks carriage returns

Added by Alexandre Anriot almost 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
1
Category:
Web - UI & UX
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

Description

Hello,

With a fresh upgrade to 3.2.8, the "Enforce a file content" technique (v7.0) breaks carriage returns in the "Content of the file" field.

If you edit an existing technique and don't save the changes, the technique keeps working.

Thanks.


Related issues

Has duplicate Rudder - Bug #9329: Newlines striped in textareasRejected2016-10-12
Has duplicate Rudder - Bug #9291: Enforce a file content - carriage returns disappear - v3.2.8Rejected2016-10-10

Associated revisions

Revision 90b61b61 (diff)
Added by Vincent MEMBRÉ almost 2 years ago

Fixes #9243: Technique "Enforce a file content" breaks carriage returns

Revision 2938d34d (diff)
Added by Vincent MEMBRÉ almost 2 years ago

Fixes #9243: Technique "Enforce a file content" breaks carriage returns

History

#1 Updated by Vincent MEMBRÉ almost 2 years ago

  • Category set to Web - UI & UX
  • Assignee set to Vincent MEMBRÉ
  • Priority changed from N/A to 1
  • Target version set to 3.1.16

I need to look if the field is now trimming inputs (but as you tell me it seems it does now ...)

A workaround: you can replace trailling lines by ${const.n}

#2 Updated by Alexandre Anriot almost 2 years ago

Thanks Vincent, I hope that I'm not mistaken.

I fixed files directly in configuration-repository/directives/fileDistribution/checkGenericFileContent/ through Git.

Vincent MEMBRÉ wrote:

I need to look if the field is now trimming inputs (but as you tell me it seems it does now ...)

A workaround: you can replace trailling lines by ${const.n}

#3 Updated by Alexandre Anriot almost 2 years ago

For the record, a restore from the archives is needed when changing a technique manually (thanks Vincent):
- Either from the archives page ;
- Or the API:

# curl -k https://localhost/rudder/api/archives/restore/full/latestCommit

Thanks Vincent, I hope that I'm not mistaken.

I fixed files directly in configuration-repository/directives/fileDistribution/checkGenericFileContent/ through Git.

Vincent MEMBRÉ wrote:

I need to look if the field is now trimming inputs (but as you tell me it seems it does now ...)

A workaround: you can replace trailling lines by ${const.n}

#4 Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from New to In progress

#5 Updated by Vincent MEMBRÉ almost 2 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/1260

#6 Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#7 Updated by Nicolas CHARLES almost 2 years ago

  • Has duplicate Bug #9329: Newlines striped in textareas added

#8 Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.2.9 and 3.1.16 which were released today.

#9 Updated by Nicolas CHARLES almost 2 years ago

  • Has duplicate Bug #9291: Enforce a file content - carriage returns disappear - v3.2.8 added

Also available in: Atom PDF