Bug #3780: Base64 entries are not supported by the migration script for 2.6 concerning the unescaping of directive contents - Rudder - Issue Tracker

Actions

Copy link

Bug #3780

closed

Base64 entries are not supported by the migration script for 2.6 concerning the unescaping of directive contents

Added by Matthieu CERDA over 11 years ago. Updated almost 10 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Matthieu CERDA

Category:

Packaging

Target version:

2.6.3

Pull Request:

https://github.com/Normation/rudder-p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

The migration script for 2.6 concerning the unescaping of directive contents does not support base64 entries, thus it skips some variables, and breaks them.

We should also support base64 entries in it !!!

This prevents the 2.6 version to reach the "stable" status and should be corrected ASAP.

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Status changed from New to Pending technical review
Assignee set to Matthieu CERDA
Priority changed from N/A to 1 (highest)
% Done changed from 0 to 100
Pull Request set to https://github.com/Normation/rudder-packages/pull/87

PR available: https://github.com/Normation/rudder-packages/pull/87

Actions

Copy link

Updated by Matthieu CERDA over 11 years ago

Status changed from Pending technical review to Pending release

Applied in changeset commit:9f25e780fe89b519a4fc686c1593fa20c53884b7.

Actions

Copy link

Updated by Jonathan CLARKE over 11 years ago

Applied in changeset commit:f5e46aff20dacc0358a52bf9f8b1a6b232879de3.

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Subject changed from The migration script for 2.6 concerning the unescaping of directive contents does not support base64 entries to Base64 entries are not supported by the migration script for 2.6 concerning the unescaping of directive contents

Actions

Copy link