Project

General

Profile

Actions

Bug #19872

closed

Rules can't be accessed directly by url, all redirection broken

Added by François ARMAND over 3 years ago. Updated about 3 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
98
Name check:
To do
Fix check:
To do
Regression:

Description

We don't have any way to access a rule directly.

For example, search anything > rule redirect toward .../secure/configurationManager/ruleManagement#{%22ruleId%22:%22db1eb3cc-e405-498c-8ade-9c7c860ce980%22} that lead to the main rule array.

Worse, when we click on a rule, we don't have an adressable link in the browser, we remain on the main one.

Actions #1

Updated by François ARMAND over 3 years ago

  • Target version changed from 7.0.0~beta1 to 900
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to First impressions of Rudder
  • Priority changed from 0 to 100
Actions #2

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 900 to 7.0.0~beta2
Actions #3

Updated by Raphael GAUTHIER over 3 years ago

  • Status changed from New to In progress
  • Assignee set to Raphael GAUTHIER
Actions #4

Updated by Raphael GAUTHIER over 3 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3875
Actions #5

Updated by François ARMAND over 3 years ago

Actually, I think we should take that opportunity to change the url scheme from

.../secure/configurationManager/ruleManagement#{%22ruleId%22:%22db1eb3cc-e405-498c-8ade-9c7c860ce980%22}

To

.../secure/configurationManager/ruleManagement/rule/db1eb3cc-e405-498c-8ade-9c7c860ce980

But I'm not sure exactly of the feature set, I think we need to also focus on a category irrespectively of a rule, so perhaps that part could remains in js, something like:

.../secure/configurationManager/ruleManagement/rule/db1eb3cc-e405-498c-8ade-9c7c860ce980#{"category":"xxxxx-e405-498c-8ade-9c7c860ce980"}
.../secure/configurationManager/ruleManagement#{"category":"xxxxx-e405-498c-8ade-9c7c860ce980"}

Or again, with url rewriting:

.../secure/configurationManager/ruleManagement/rule/db1eb3cc-e405-498c-8ade-9c7c860ce980?category=xxxxx-e405-498c-8ade-9c7c860ce980
.../secure/configurationManager/ruleManagement?category=xxxxx-e405-498c-8ade-9c7c860ce980

Actions #6

Updated by Raphael GAUTHIER over 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #7

Updated by Vincent MEMBRÉ about 3 years ago

  • Status changed from Pending release to Released
  • Priority changed from 100 to 98

This bug has been fixed in Rudder 7.0.0~beta2 which was released today.

Actions

Also available in: Atom PDF