[jboss-jira] [JBoss JIRA] (WFWIP-317) [EAP7-1457] backward compatibility breaking change in EAP Operator API

[Petr Kremensky (Jira)]

    [ https://issues.redhat.com/browse/WFWIP-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065636#comment-14065636 ] 

Petr Kremensky commented on WFWIP-317:
--------------------------------------

Note we've already released EAP Operator release 1.0 twice:

1) https://errata.devel.redhat.com/advisory/48030 RHEA-2019:4236-04   EAP Operator release 1.0 - "jboss-eap-7-eap73-operator-container-1.0-7" image
 * QE gave a sign off to this https://mojo.redhat.com/docs/DOC-1212528 as EAP Operator release 1.0
 * was claimed to be fully supported http://postoffice.corp.redhat.com/archives/eap-pm-list/2019-December/msg00053.html
 * but ultimately switched to TP https://issues.redhat.com/browse/EAP7-1258?focusedCommentId=13941877&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13941877

2) https://errata.devel.redhat.com/advisory/53172 RHEA-2020:1329-04   EAP Operator release 1.0 - "jboss-eap-7-eap73-operator-container-1.0-8" image
 * https://issues.redhat.com/browse/JBEAP-19105
 * Release Category: Generally Available https://catalog.redhat.com/software/containers/detail/5dc0529ebed8bd164af4cc8a

> [EAP7-1457] backward compatibility breaking change in EAP Operator API
> ----------------------------------------------------------------------
>
>                 Key: WFWIP-317
>                 URL: https://issues.redhat.com/browse/WFWIP-317
>             Project: WildFly WIP
>          Issue Type: Quality Risk
>          Components: OpenShift
>            Reporter: Petr Kremensky
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> [EAP Operator release 1.0|https://catalog.redhat.com/software/containers/detail/5dc0529ebed8bd164af4cc8a]
>  * Release Category: Generally Available 
>  * https://errata.devel.redhat.com/advisory/53172
> https://github.com/wildfly/wildfly-operator/pull/136 is into introduce a breaking change in API (see https://github.com/wildfly/wildfly-operator/pull/136#issuecomment-620584823). The reasoning for this is that the current version of API is "wildfly.org/v1alpha1" so can still can afford to do it (see https://github.com/wildfly/wildfly-operator/pull/136#issuecomment-620590664).
> Although I personally think that https://issues.redhat.com/browse/EAP7-1457 is a good improvement, I do not (and as a QE I even cannot) like the fact that we can break the existing user deployments by breaking the API compatibility with 1.0 Final EAP Operator release (although our operator is still pretty young and I'm not sure how many deployments that would actually be).
> We should have an explicit approval from PM/GSS in order to carry on - breaking the API compatibility by https://github.com/wildfly/wildfly-operator/pull/136 



--
This message was sent by Atlassian Jira
(v7.13.8#713008)