Skip to content

feat!: support 'source' property in Interceptor #99

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

Open
wants to merge 26 commits into
base: development
Choose a base branch
from

Conversation

Pasichniuk
Copy link
Contributor

@Pasichniuk Pasichniuk commented Jul 22, 2025

Applicable issues

Description of changes

BREAKING CHANGE: 'interceptorRunner' property is removed from Interceptor. Instead, 'source' property is added.

Source can be of three types: endpoints, runner or container.
When source is container, endpoint base URL is retrieved from MCP manager. Interceptor endpoints are refreshed on schedule to handle the case when container URL changes.

Checklist

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

}

private DeploymentInfoDto getDeploymentInfoDto(String id) {
if (StringUtils.isBlank(deploymentClientUrl)) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Could you please clarify the purpose of the custom exception?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Because none of existing fits. What's the problem?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I mean why do we need to separate case when deploymentClientUrl is not set from any other cases?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

InterceptorImporter line 89

Copy link
Collaborator

@KirylKurnosenka KirylKurnosenka Jul 25, 2025

Choose a reason for hiding this comment

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

Just to log warning message "Failed to get deployment" instead of logging error message?
When DeploymentClientNotExistsException is thrown, deploymentInfo in InterceptorImporter stays null, when any other exception is thrown error message is logged in this class but deploymentInfo in InterceptorImporter still stays null

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's important to know that deployment was expected, but wasn't found. We have plans to have pop-up warning messages on FE that will inform about issues during endpoints refresh/unsuccessful import of interceptors linked to containers

@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

# Conflicts:
#	src/test/java/com/epam/aidial/cfg/functional/tests/ConfigTransferFunctionalTest.java
@ai-dial-actions
Copy link
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

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.

4 participants