Bug 2084438

Summary: Change Ping source spec.jsonData (deprecated) field to spec.data
Product: OpenShift Container Platform Reporter: Karthik Jeeyar <kjeeyar>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: Jaivardhan Kumar <jakumar>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: cjerolim, divgupta, jakumar, nmukherj, viraj
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Deprecated Functionality
Doc Text:
For the Ping source, `jsonData` property has been deprecated and replaced with `data`.
 Story Points: ---
Clone Of:
: 2094211 (view as bug list) Environment:
Last Closed: 2022-08-10 11:11:30 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:
Bug Depends On:    
Bug Blocks: 2094211    
Attachments:
Description Flags
Ping source yaml view none

Description Karthik Jeeyar 2022-05-12 07:03:01 UTC 
Created attachment 1878859 [details]
Ping source yaml view

Description of problem:

Creating Ping source, with data field is internally mapping it to spec.jsonData field, which is deprecated and on submission the key is removed automatically by the controllers.


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

How reproducible:
Always

Steps to Reproduce:
1. Go to EventSource -> Ping Source form
2. Add a value to the data field in the form view
3. Switch to yaml view to see the jsonData field
4. Click on create button.

Actual results:

spec.jsonData field will be removed automatically from the newly created ping source object.

Expected results:

After changing the spec.jsonData to spec.data then on creation of a ping source should contain the spec.data field.



Additional info:

Ping source API spec: https://knative.dev/docs/eventing/sources/ping-source/reference/#pingsource
Comment 4 Jaivardhan Kumar 2022-06-09 10:45:18 UTC 
Verified on 4.11.0-0.nightly-2022-06-06-201913, works as expected
Comment 6 errata-xmlrpc 2022-08-10 11:11:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069