Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#519: Add configuration for step customization #563

Merged
merged 6 commits into from
Apr 3, 2024

Conversation

kaklakariada
Copy link
Collaborator

Part of #519

Copy link
Collaborator

@ckunki ckunki left a comment

Choose a reason for hiding this comment

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

Should we update the requirements / design documents, too?
(optionally in a separate PR)

/** Insert the step after the configured step ID. */
INSERT_AFTER,
/** Replace the step with the new one. */
REPLACE
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could there also be INSERT_BEFORE and DELETE?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, that's possible. But I don't think we need it at the moment.


private final Map<String, Object> rawStep;

private WorkflowStep(final Map<String, Object> rawStep) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there a specific reason for the constructor being private and offering a static method for instantiation?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We might want to add some validation in the future.

Copy link
Collaborator

@ckunki ckunki left a comment

Choose a reason for hiding this comment

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

Did I observe correctly that actually applying customizations, specified in file .project-keeper.yml to existing workflow files is planned to be implemented in a separate PR?

@kaklakariada kaklakariada enabled auto-merge (squash) April 3, 2024 07:59
Copy link

sonarcloud bot commented Apr 3, 2024

@kaklakariada kaklakariada merged commit 06abdd7 into main Apr 3, 2024
8 checks passed
@kaklakariada kaklakariada deleted the feature/#519-config branch April 3, 2024 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants