feat(DATAGO-130052): Add model dependents functionality with endpoint for retrieving dependent agents#1281
Open
feat(DATAGO-130052): Add model dependents functionality with endpoint for retrieving dependent agents#1281
Conversation
✅ FOSSA Guard: Licensing (
|
✅ FOSSA Guard: Vulnerability (
|
|
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
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 is the purpose of this change?
Add support for safely deleting model configurations by providing a mechanism to identify and handle agent dependencies before deletion. This helps prevent broken deployments when a model configuration is removed while agents are still using it.
How was this change implemented?
High-level approach:
ModelDependentsHandlerinterface that enterprise code can implementGET /models/{alias}/dependentsto list agents using a modelDELETE /models/{alias}to automatically undeploy dependent agentsKey commits:
Key Design Decisions
How was this change tested?
Is there anything the reviewers should focus on/be aware of?
The enterprise implementation details are handled in a separate repository, this PR only adds the interface and community version.