Skip to content

[ENH]: fix sysdb S3 config for parity between local dev & deployed env, add necessary params #4202

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

Merged
merged 2 commits into from
Apr 7, 2025

Conversation

codetheweb
Copy link
Contributor

@codetheweb codetheweb commented Apr 7, 2025

Description of changes

Updates sysdb S3 config flags to improve parity between local dev and deployed envs. Also adds parameters necessary for configuration in deployed env (bucket name) and verifies that bucket is accessible before continuing startup.

Test plan

How are these changes tested?

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

n/a

Copy link

github-actions bot commented Apr 7, 2025

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Copy link

github-actions bot commented Apr 7, 2025

⚠️ The Helm chart was updated without a version bump. Your changes will only be published if the version field in k8s/distributed-chroma/Chart.yaml is updated.

@codetheweb codetheweb marked this pull request as ready for review April 7, 2025 19:37
@codetheweb codetheweb force-pushed the fix-sysdb-s3-config branch from 5e11444 to bb45683 Compare April 7, 2025 19:54
@codetheweb codetheweb enabled auto-merge (squash) April 7, 2025 20:43
@codetheweb codetheweb merged commit 32e414e into main Apr 7, 2025
82 checks passed
@codetheweb codetheweb deleted the fix-sysdb-s3-config branch April 7, 2025 20:53
philipkiely-baseten pushed a commit to philipkiely-baseten/chroma that referenced this pull request Apr 8, 2025
…v, add necessary params (chroma-core#4202)

## Description of changes

Updates sysdb S3 config flags to improve parity between local dev and
deployed envs. Also adds parameters necessary for configuration in
deployed env (bucket name) and verifies that bucket is accessible before
continuing startup.

## Test plan
*How are these changes tested?*

- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Documentation Changes
*Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
repository](https://github.com/chroma-core/docs)?*

n/a
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.

2 participants