[Do Not Merge] feat: add support for existing custom resolver #966
Conversation
This file contains hidden or 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
imprateeksh
requested review from
maheshwarishikha and
rajatagarwal-ibm
as code owners
rajatagarwal-ibm
requested changes
Apr 16, 2025
Member
|
@imprateeksh no need to create an example for this as there's already delegated example in place. |
Member
Author
|
/run pipeline |
Member
Author
|
/run pipeline |
Member
Author
|
PR run failed as some error while initializing containers. Will re-run again. |
Member
Author
|
/run pipeline |
imprateeksh
changed the title
Member
Author
|
Please Do not merge the PR as we are waiting on HPC teams' response. Details are provided in the issue. |
Member
Author
|
Closing the PR as mentioned here |
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.
Description
This PR includes the changes to support existing custom resolver.
Refer Issue : #13199
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers