Bug 1775719 - default template for metering report for editor should use v1 instead of v1apha1
Summary: default template for metering report for editor should use v1 instead of v1apha1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.3.0
Assignee: David Taylor
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1772694 1776339
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-22 16:20 UTC by David Taylor
Modified: 2019-11-25 13:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1772694
: 1775720 (view as bug list)
Environment:
Last Closed: 2019-11-22 16:30:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Taylor 2019-11-22 16:20:52 UTC 
+++ This bug was initially created as a clone of Bug #1772694 +++

Description of problem:
The default report and ReportQuries generated by the UI that populated the UI editor should ue `v1` instead of `v1alpha``.  The resulting report can still be generated but we should use the proper versioning going forward in case support for `v1apha1` is dropped.

Version-Release number of selected component (if applicable):
OCP >= 4.2

How reproducible:
always

Steps to Reproduce:
1.  Have metering installed.
2.  Administration->Chargeback
3.  Click on Create / CreateReportQuery
4.  The default template will show that it's using `v1alpha1`

This applies to creating a Report as well as ReportQuery
https://github.com/openshift/console/blob/41940c686cf55c8ed6331b539c9f78b8f49d174b/frontend/public/models/yaml-templates.ts#L200

https://github.com/openshift/console/blob/41940c686cf55c8ed6331b539c9f78b8f49d174b/frontend/public/models/yaml-templates.ts#L212

Actual results:
apiVersion: metering.openshift.io/v1alpha1

Expected results:
apiVersion: metering.openshift.io/v1


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