Agentspace GcsArtifactService vs InMemoryArtifactService #3308
                  
                    
                      onix-rdeandrade
                    
                  
                
                  started this conversation in
                General
              
            Replies: 0 comments
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
I have an agent that implements GCS for artifacts:
`# Deploy the agent with GcsArtifactService.
def set_gcs_artifact_service(agent, artifact_bucket_name):
def artifact_service_builder():
return GcsArtifactService(bucket_name=artifact_bucket_name)
return AdkApp(
agent=agent,
artifact_service_builder=artifact_service_builder,
)
agent_with_gcs_artifact_service = set_gcs_artifact_service(
root_agent,
ARTIFACT_BUCKET_NAME,
)`
But when called from Agentspace (aka Gemini Enterprise) the logs still show the InMemory service is being used:
/home/appuser/.cache/pypoetry/virtualenvs/reasoning-engine-assembly-service-MATOk_fk-py3.12/lib/python3.12/site-packages/vertexai/preview/reasoning_engines/templates/adk.py:587: UserWarning: [EXPERIMENTAL] InMemoryCredentialService: This feature is experimental and may change or be removed in future versions without notice. It may introduce breaking changes at any time.This seems to be the same on 1.16 and 1.17. Note that 1.17 is currently broken for agentspace and file uploads.
Am I understanding this wrong (or implemented it wrong?) ? Shouldn't the service at the startup be the GCS one? Glad to open as a bug if this is one.
Beta Was this translation helpful? Give feedback.
All reactions