feat: Add a 'JobBundlePurpose' type. #94
Merged
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
Signed-off-by: Ramon Montoya Vozmediano <1171039+rmv@users.noreply.github.com>
This was referenced Oct 26, 2023
rcajigal
approved these changes
Oct 26, 2023
amznestebanpapp
approved these changes
Oct 27, 2023
jlangmann-aws
approved these changes
Oct 27, 2023
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.
What was the problem/requirement? (What/Why)
Bundle creation callback needs to be able to report the purpose for the bundle's creation.
What was the solution? (How)
This is part 1 of the change required in bealine-cloud. This type will be used by submitters to determine the current task (submit or export) see #92
What is the impact of this change?
Will make it possible to do DCC specific tests on submission, or to only do telemetry for submissions.
How was this change tested?
This was tested as part of #92
Was this change documented?
No
Is this a breaking change?
No