Skip to content
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.

Add task for deploying application manifests #392

Merged

Conversation

masayag
Copy link
Collaborator

@masayag masayag commented May 31, 2023

What this PR does / why we need it:
The PR adds a workflow task to read manifests from a given path and apply them to OCP cluster.
Once the resources are applied, the work context should be updated with the routers to the deployed application.

Which issue(s) this PR fixes:
Fixes FLPATH-411

Change type

  • New feature
  • Bug fix
  • Unit tests
  • Integration tests
  • CI
  • Documentation
  • Auto-generated SDK code

Impacted services

  • Workflow Service
  • Notification Service

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.

Copy link
Collaborator

@eloycoto eloycoto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing test.

@masayag
Copy link
Collaborator Author

masayag commented May 31, 2023

Missing test.

@eloycoto before writing tests, I wanted to make sure the expectation for the input parameters is correct

@eloycoto
Copy link
Collaborator

@eloycoto before writing tests, I wanted to make sure the expectation for the input parameters is correct

Overall LGTM, maybe I'll move the set manifest to a public function; I can think of extending the class without parameters and deploying the manifest directly into it.

@masayag masayag force-pushed the m2k_deploy_app branch 2 times, most recently from 8d6bcfd to bf22896 Compare June 2, 2023 08:46
The PR adds a workflow task to read manifests from a given path and
apply them to OCP cluster.

Once the resources are applied, the work context should be updated with
the routers to the deployed application.

Signed-off-by: Moti Asayag <masayag@redhat.com>
@masayag
Copy link
Collaborator Author

masayag commented Jun 4, 2023

@eloycoto before writing tests, I wanted to make sure the expectation for the input parameters is correct

Overall LGTM, maybe I'll move the set manifest to a public function; I can think of extending the class without parameters and deploying the manifest directly into it.

feel free to modify the code as you see once it is merged to satisfy the needs of the next evolution of it, or let me know what you'd like me to change.

@masayag masayag requested a review from eloycoto June 5, 2023 07:44
@eloycoto
Copy link
Collaborator

eloycoto commented Jun 5, 2023

/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Jun 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eloycoto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Jun 5, 2023
@openshift-merge-robot openshift-merge-robot merged commit 03f31fc into rhdhorchestrator:main Jun 5, 2023
@pkliczewski
Copy link
Collaborator

@ydayagi it would be good to use this client instead

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants