Skip to content
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

[ENH]: AWS Terraform Blueprint Improvements #1173

Merged

Conversation

tazarov
Copy link
Contributor

@tazarov tazarov commented Sep 22, 2023

Refs: #1172 and #1135

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • Added support for restoring from snapshot
      • Added snapshotting volume before destroy
      • Bumped default Chroma version to 0.4.12
      • Added support for persistent volume mounts (in fstab)
      • Improved tagging
      • Made source ranges for the Security Group configurable
      • Made external Chroma port configurable
      • Switched to use a GH startup script.

Test plan

How are these changes tested?

Tests not yet executed.

Documentation Changes

Updated README.md of the blueprint

- Added support for restoring from snapshot
- Added snapshotting volume before destroy
- Bumped default Chroma version to 0.4.12
- Added support for persistent volume mounts (in fstab)
- Improved tagging
- Made source ranges for the Security Group configurable
- Made external Chroma port configurable
- Switched to use a GH startup script.

Refs: chroma-core#1172
@github-actions
Copy link

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 (Readbility, Modularity, Intuitiveness)

beggers added a commit that referenced this pull request Sep 22, 2023
## Description of changes

`lifecycle` blocks don't allow variables. Right now our example
deployment for AWS doesn't work. @tazarov has a fix for this and a few
other things in #1173 but I'd
like to get the basic fix out before the weekend.

## Test plan
local `terraform init` failed before, now works.

## 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)?*
Copy link
Contributor

@beggers beggers left a comment

Choose a reason for hiding this comment

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

Awesome work! I'm really happy to see us expanding our example deployments

@beggers beggers merged commit 2dcffca into chroma-core:main Oct 2, 2023
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