Added quarkus/v1-alpha plugin

[laxmikantbpandhare]

Description of the change:
This change will enable the command for Java Plugin.

Motivation for the change:
Implementation of Java Operator's in Operator Framework.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• Add or update relevant sections of the docs website in website/content/en/docs

[camilamacedo86]

It is missing:

• changelog (fragment)
• sample in the testdata with the java plugin such as it has for go/helm/ansible
  -e2e tests such as it has for go/helm/ansible

Note that is not passing in the sanity because you need to run make generate to re-gen docs.

[jmrodri]

@camilamacedo86 the samples live in the plugins repo: https://github.com/operator-framework/java-operator-plugins/tree/main/testdata/memcached-quarkus-operator

and it is a v1alpha so it will likely go through massive changes

[estroz]

Agreed, samples do not need to live in the operator-sdk repo if the plugin is external. Still needs a changelog, and make sure to specify that this plugin is alpha and subject to breaking changes.

[camilamacedo86]

HI @jmrodri, @estroz

How will we ensure that SDK is generating that properly? So, I think we need a sample in the SDK repo. Also, how we will check its default result and compare the changes and etc? Note that check the samples scaffold is very helpful in the review and development process as we are able to share an example with the users as well.

Also, should we not ensure that the java plugin generated with SDK also pass in the e2e tests such as is deployed, scorecard, bundle tests and etc?

[estroz]

How will we ensure that SDK is generating that properly?

Because operator-sdk calls the plugin directly from its repo, which should be creating sample code itself. I do not want one sample per external plugin, as Operator SDK does not necessarily own nor maintain those plugins. That just isn't scalable.

Also, should we not ensure that the java plugin generated with SDK also pass in the e2e tests such as is deployed, scorecard, bundle tests and etc?

We can add integration tests for these, but a checked-in sample is not a requirement for integration tests. These tests can be added in a follow-up since the plugin is very much alpha.

^

[varshaprasad96]

@laxmikantbpandhare you may have to run make generate to generate the samples again after the change.

[laxmikantbpandhare]

@laxmikantbpandhare you may have to run make generate to generate the samples again after the change.

Yes, I already did and then only did commit. But, sanity is still failing. I will try once again.

[laxmikantbpandhare]

It is missing:

• changelog (fragment)
• sample in the testdata with the java plugin such as it has for go/helm/ansible
  -e2e tests such as it has for go/helm/ansible

Note that is not passing in the sanity because you need to run make generate to re-gen docs.

Added changelog (fragment)

[estroz]

I rebased your commit onto master locally, ran make generate, and saw testdata revert.

[estroz]

/lgtm

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[estroz]

/lgtm