Graylog2 / Graylog2/graylog2-server
Content Pack Install modal shows different order of Parameters depending on what page launched the "install" modal
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
Content Pack Install modal shows different order of Parameters depending on what page launched the "install" modal
There are at least 2 places (in the UI) that allow a user to install a Graylog Content Pack:
- on the page that shows the list of content packs (`/system/contentpacks`)
- on the page for that specific content pack (`/system/contentpacks/`)
### The `/system/contentpacks` modal:
parameters (appears to be sorted ascending):
- HTTP Auth Header
- Graylog API License Usage URL
- Graylog API License Size URL
### The `/system/contentpacks/` modal:
parameters (appears to be sorted descending):
- Graylog API License Size URL
- Graylog API License Usage URL
- HTTP Auth Header
## Expected Behavior
Sorting of Configure Parameter is the same regardless of what Install modal is used
## Current Behavior
Sorting of Configure Parameter varies depending on what Install modal is used
## Possible Solution
## Steps to Reproduce (for bugs)
1.
2.
3.
4.
## Context
Minor but ran across this when drafting customer documentation.
## Your Environment
* Graylog Version: 6.3.3
* Browser version: Version 141.0.7390.78 (Official Build) (arm64)
## Checklist
[] This issue fix need to be backported.
[] Does this issue have **security** implications?
Contributor guide
Assessment
This issue has not been assessed yet.