Project

General

Profile

Actions

Bug #14041

closed

Bug #14038: Separated policy generation does not work correctly with Rudder DSC agent

Replace all RudderUniqueID in paths for inputs list and rudder.json, and correctly generate paths based on agent type

Added by Nicolas CHARLES almost 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

If we use RudderUniqueID in outpath, then the file is at the correct location, but both the input list and the rudder.json still contain the RudderUniqueId

and with dsc agent, we currently need a proper outpath, ortherwise we get policy with a .ps1.cf, which dsc agent cannot read, so we need to correctly support that

Actions #1

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #2

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2103
Actions #3

Updated by Rudder Quality Assistant almost 6 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from François ARMAND to Nicolas CHARLES
Actions #4

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from Discussion to Pending release
Actions #5

Updated by Vincent MEMBRÉ almost 6 years ago

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

Also available in: Atom PDF