add DeploymentConfigRollback object to openshift model

[mluckam]

Description

added DeploymentConfigRollback object to openshift model
https://docs.openshift.com/container-platform/4.10/rest_api/workloads_apis/deploymentconfigrollback-apps-openshift-io-v1.html

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[rohanKanojia]

@mluckam : Could you please add a test for this? See existing tests.

[mluckam]

@rohanKanojia unit test has been added.

[rohanKanojia]

Is .withNewSpec() available here?

  .withNewSpec()
     .withFrom( )
  .endSpec

[mluckam]

Yes it is. This helps reduce the nesting. Thanks for the idea.

[rohanKanojia]

Why not use ObjectReferenceBuilder here?

[mluckam]

Oversight, will update.

[rohanKanojia]

@mluckam : What is the use case for this change? How do you plan to use this object from openshift-model? Do you also plan to make subsequent changes in OpenShiftClient DSL ?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[mluckam]

The DeploymentConfigRollback is utilized to rollback a DeploymentConfig via the API path "/apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}/rollback", see documentation. The model DeploymentConfigRollback was not currently in this project, but available in the dependent model project.

Currently I am migrating to utilizing the kubernetes and openshift models from this project. Once the models from this project are utilized, a next step would be to transition from interacting with the API via an HTTP client, to utilizing the OpenShiftClient. This may be several months away though. Until this migration occurs, I do not have plans to update the OpenShiftClient DSL.

[rohanKanojia]

@mluckam : Could you please create an issue for /rollback support in OpenShiftClient DSL?

[manusa]

LGTM, thx!