Bug 1698383 - [RFE] Unify Web UI distro url import behavior with CLI distro-import
Summary: [RFE] Unify Web UI distro url import behavior with CLI distro-import
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 27.0
Assignee: Matej Dujava
QA Contact: tools-bugs
URL:
Whiteboard:
: 1198948 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-10 09:38 UTC by Tomas Klohna 🔧
Modified: 2019-10-22 13:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 13:54:13 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Beaker Project Gerrit 6487 0 'None' 'ABANDONED' 'Unify web distro import with CLI distro import' 2019-12-04 12:00:32 UTC
Beaker Project Gerrit 6651 0 'None' 'MERGED' 'Unify web distro import with CLI distro import' 2019-12-04 12:00:32 UTC

Description Tomas Klohna 🔧 2019-04-10 09:38:23 UTC
Import Distro Tree URL in Web behaves differently and has separate code from the distro-import CLI. Some of this behavior can be unified so they both behave the same.

For instance:
* Importing duplicate URL through CLI will lead to distro-import skipping over that URL but doing this in Web UI will result in error (500, should be fixed as part of this bug.
* Importing URL with same scheme that is already present in said distro tree will lead to distro-import replacing the old URL with the new one. Doing this in Web UI will result in multiple URLs with the same scheme (that should never happen)
* There is non-functional part in the distro-import code that's supposed to be checking if URL is not absolute. Right now it's not working but works correctly in the Web UI. Should be fixed and unified as well.

Comment 1 Tomas Klohna 🔧 2019-04-10 09:39:24 UTC
*** Bug 1198948 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.