Bug 1716701

Summary: Add back ability to modify deployment config options like triggers in the web console
Product: OpenShift Container Platform Reporter: Jan Kleinert <jkleiner>
Component: RFEAssignee: Paul Weil <pweil>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-12 11:59:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
deployment config triggers none

Description Jan Kleinert 2019-06-04 01:00:00 UTC
Created attachment 1576797 [details]
deployment config triggers

Description of problem:
In the past (e.g. v3.11), there was a deployment configuration tab where things like image change triggers and config change triggers could be enabled and disabled. This is not available in v4, so the user must go into the YAML and add/edit/delete these. This requires knowing what the appropriate YAML syntax is.


Version-Release number of selected component (if applicable):


How reproducible:
consistently

Steps to Reproduce:
1. Go to a deployment config page and look for a configuration tab or a way to edit triggers in the UI


Actual results:
In the UI, the only way to do this is to edit the YAML.

Expected results:
A deployment config page with options for modifying things like image change triggers and config change triggers.

Additional info:
see attachment.

Comment 1 Kirsten Newcomer 2019-06-12 11:59:24 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.