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

Petr Kremensky (Jira) issues at jboss.org
Wed Apr 29 04:40:00 EDT 2020


Petr Kremensky created WFWIP-317:
------------------------------------

             Summary: [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


[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)


More information about the jboss-jira mailing list