[SELC-5642] feat: added new workflow executor for GPU #621
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
November 25, 2024 11:09
…into feature/SELC-5642
…into feature/SELC-5642
added 3 commits
November 27, 2024 11:08
…into feature/SELC-5642 � Conflicts: � apps/onboarding-functions/src/main/java/it/pagopa/selfcare/onboarding/functions/OnboardingFunctions.java � apps/onboarding-functions/src/test/java/it/pagopa/selfcare/onboarding/functions/OnboardingFunctionsTest.java
pierpaolodidato89
temporarily deployed
to
dev-cd
GitHub Actions
Inactive
added 2 commits
November 28, 2024 12:42
…into feature/SELC-5642
pierpaolodidato89
changed the title
gianmarcoplutino
approved these changes
Nov 28, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List of Changes
Added new workflow executor to manage the onboarding of GPU
Motivation and Context
This workflow is separated from similar ones - FOR_APPROVE and FOR_APPROVE_PT - considering the new orchestation function that will manage attachments.
How Has This Been Tested?
I have deployed the feature in DEV and tested the onboarding from frontend, checking corresponding values into DB
Screenshots (if appropriate):
Types of changes
Checklist: