Project

General

Profile

Actions
Copy link

Bug #19437

closed

Fix docs about HTTPS reporting in non-compliant mode

Added by Alexis Mousset about 4 years ago. Updated about 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Documentation
Target version:
6.1.14
Pull Request:
https://github.com/Normation/rudder-d...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

It is possible since 6.1 and https://issues.rudder.io/issues/17153.

Actions
Copy link
 #1

Updated by Alexis Mousset about 4 years ago

  • Status changed from New to In progress
  • Assignee set to Alexis Mousset
Actions
Copy link
 #2

Updated by Alexis Mousset about 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/831
Actions
Copy link
 #3

Updated by Alexis Mousset about 4 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #4

Updated by Alexis Mousset about 4 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.14 and 6.2.8 which were released today.

Actions
Copy link

Also available in: Atom PDF