-
Notifications
You must be signed in to change notification settings - Fork 4
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
Added resource group isolation to DeploymentCache #103
Conversation
.orElseThrow( | ||
() -> | ||
new NoSuchElementException( | ||
"No running deployment found for scenario: " + scenarioId)); | ||
}); | ||
} | ||
|
||
private Optional<String> getDeploymentIdByScenario(@Nonnull final String scenarioId) { | ||
return CACHE.stream() | ||
private Optional<String> getDeploymentIdByScenario( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(minor) It would be nice to stick to either VAVRs Option<>
or Javas Optional
. Mixing the two is a bit awkward, and mixing them in public API might be confusing for users. In Cloud SDK we used VAVR because it's more powerful and integrated with Try
etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not public API it's just a private helper function to reduce code duplication.
Context
AI/ai-sdk-java-backlog#54.
The deployment cache needs to isolate between resource groups.
Also customers should be able to reset the cache
Feature scope:
AiCoreService.resetCache(client, resourceGroup)
Definition of Done
Aligned changes with the JavaScript SDKDocumentation updatedRelease notes updated