Project

General

Profile

Actions

action #37042

closed

Implement feature to override beta flag for SLE modules in proxy SCC

Added by riafarov over 6 years ago. Updated 10 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Target version:
QA (public, currently private due to #173521) - future
Start date:
2018-06-11
Due date:
% Done:

0%

Estimated time:

Description

Motivation

During GMC phase we have issue that product is considered to be non-beta (no beta warnings in installer, etc.). However, as we use production SCC in the end, modules are still shown as beta, as officially product is still in the beta phase.
Proxy SCC proxies all requests received from SCC, and we can override this data.

Acceptance criteria

  1. Proxy SCC allows to override beta flag for modules

Suggestions

Communicate this request to SCC team as they may implement this feature, depending on the load.

Actions #1

Updated by okurz over 6 years ago

  • Subject changed from [sle][functional][proxy-scc] Implement feature to override beta flag for SLE modules in proxy SCC to [sle][functional][y][proxy-scc] Implement feature to override beta flag for SLE modules in proxy SCC
  • Target version set to Milestone 19
Actions #2

Updated by okurz over 6 years ago

  • Target version changed from Milestone 19 to Milestone 19
Actions #3

Updated by okurz about 6 years ago

  • Target version changed from Milestone 19 to future

I see only limited value in this feature as we are talking about a short time frame where this would help.

Actions #4

Updated by riafarov about 4 years ago

  • Project changed from openQA Tests (public) to qe-yam
  • Subject changed from [sle][functional][y][proxy-scc] Implement feature to override beta flag for SLE modules in proxy SCC to Implement feature to override beta flag for SLE modules in proxy SCC
  • Category deleted (Infrastructure)
Actions #5

Updated by okurz about 3 years ago

  • Priority changed from Normal to Low

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)

Actions #6

Updated by JERiveraMoya 10 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions

Also available in: Atom PDF