Bug #3113: (ex PT/ Technique)ManageFileAndFolder: Symlinks cannot be applied if another symlink, file or folder is already existing with the same path than the symlink - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open issues 8.0
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #3113

closed

(ex PT/ Technique)ManageFileAndFolder: Symlinks cannot be applied if another symlink, file or folder is already existing with the same path than the symlink

Added by Nicolas PERRON over 11 years ago. Updated about 9 years ago.

Status:

Released

Priority:

Assignee:

Nicolas CHARLES

Category:

Techniques

Target version:

2.3.10

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

We should be able to force the Technique Manage a file or a folder to create a symlink, even if there is already a symlink, file or folder.

Pull Request URL: https://github.com/Normation/rudder-techniques/pull/21

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

Description updated (diff)
Status changed from New to Pending technical review
% Done changed from 0 to 100

Add Pull Request URL: https://github.com/Normation/rudder-techniques/pull/21

Actions

Copy link

Updated by Nicolas PERRON over 11 years ago

I've use the attribute move_osbtructions of the promise type files:

The note about this attribute in the CFE3 Reference Manual is:

If we have promised to make file X a link, but it already exists as a file, or vice-versa, or if a file is blocking the creation of a directory etc, then normally CFEngine will report an error. If this is set, existing objects will be moved aside to allow the system to heal without intervention. Files and directories are saved/renamed, but symbolic links are deleted.

Actions

Copy link