Bug #2471: PT filePermissions has Owner and Group values mandatory even if our choice is to not modify them - Rudder - Issue Tracker

Custom queries

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

Actions

Copy link

Bug #2471

closed

PT filePermissions has Owner and Group values mandatory even if our choice is to not modify them

Added by Nicolas PERRON almost 13 years ago. Updated about 10 years ago.

Status:

Released

Priority:

Assignee:

Matthieu CERDA

Category:

Techniques

Target version:

2.3.9

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

This happen in Rudder 2.3 with filePermissions 1.0

Files

1.png (216 KB) 1.png

Jonathan CLARKE, 2012-07-05 17:37

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jonathan CLARKE almost 13 years ago

Project changed from Rudder to 24
Category deleted (~~Techniques~~)

Actions

Copy link

Updated by Jonathan CLARKE almost 13 years ago

Assignee changed from Jonathan CLARKE to Matthieu CERDA

Actions

Copy link

Updated by Matthieu CERDA almost 13 years ago

Status changed from New to Discussion
Assignee changed from Matthieu CERDA to Nicolas PERRON

I'm sorry, but when I try to create a Policy Instance with this PT without ticking the "Should the owner of the file be modified ?" box by example, everything goes fine.

Can you please elaborate more on what you saw ?

Actions

Copy link

Updated by Nicolas PERRON over 12 years ago

This bug is no more repetable. We should reject it

Actions

Copy link

Updated by Nicolas PERRON over 12 years ago

Category set to Policy Templates

And it concerns Policy Templates

Actions

Copy link

Updated by Jonathan CLARKE over 12 years ago

File 1.png 1.png added
Assignee changed from Nicolas PERRON to Matthieu CERDA

Nicolas PERRON wrote:

This bug is no more repetable. We should reject it

I disagree, the problem is still present.

To elaborate on it: this Technique (PT) has a checkbox "Should the owner of the file be modified ?". If you don't select it, you still have to put a value in the field "Owner of the file", which is not optional.

See the screenshot of an attempt to save a new Directive based on this Technique without specifying a user:

Actions

Copy link