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

fix workflow name #97

Merged
merged 1 commit into from
Mar 13, 2023
Merged

Conversation

RichardW98
Copy link
Contributor

@RichardW98 RichardW98 commented Mar 13, 2023

fix workflow name
workflow name should be consistent with its bean name for aspect discovery

@@ -66,7 +66,7 @@ WorkFlow assessmentWorkFlow(
@Qualifier("onboardingAssessmentTask") OnboardingAssessmentTask onboardingAssessmentTask) {
// @formatter:off
return SequentialFlow.Builder.aNewSequentialFlow()
.named("onboarding Assessment WorkFlow")
.named("onboardingAssessment" + WorkFlowConstants.ASSESSMENT_WORKFLOW)
Copy link
Collaborator

Choose a reason for hiding this comment

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

A question about this one: Isn't it redundant to specify the workflow type by annotation and also by the name?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good question Moti! its name is just a metadata and it should be consistent from bean to builder(basically you can give a workflow any name). Annotation is which type it really is, we need to process a workflow based on its annotated type(e.g. assessment should return options, checker should run on a schedule for certain tasks and so on).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

let me know if it makes sense

Copy link
Contributor

@anludke anludke Mar 13, 2023

Choose a reason for hiding this comment

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

@masayag Workflow type in parados is either Infrastructure, Assessment and Checker. Annotations have been introduced to make that distinction including the need for additional metadata. On the other hand, workflow processing type (Sequential or Parallel) is derived form the workflow bean. Hope that helps clarifying the workflow type part.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Workflow type in parados is either Infrastructure, Assessment and Checker. Annotations

and Escalation since the weekend ;-)

Thank you both for your replies. That makes sense to me.

@masayag
Copy link
Collaborator

masayag commented Mar 13, 2023

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Mar 13, 2023

@masayag: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link
Contributor

@gciavarrini gciavarrini left a comment

Choose a reason for hiding this comment

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

lgtm

@openshift-ci
Copy link

openshift-ci bot commented Mar 13, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gciavarrini, RichardW98

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 lgtm label Mar 13, 2023
@RichardW98 RichardW98 merged commit 8f3c9af into parodos-dev:main Mar 13, 2023
@RichardW98 RichardW98 deleted the fix-workflow-name branch March 13, 2023 13:53
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