Conda-store relies on PostgreSQL instance to run as part of its backend; currently, if not explicitly added to the host_vars variables, this will not be deployed by default. Which breaks the conda-store server service
Put a x in the boxes that apply
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):
Testing
[ ] Did you test the pull request locally?
[ ] Did you add new tests?
Documentation
Access-centered content checklist
Text styling
[ ] The content is written with plain language (where relevant).
[ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[ ] All links describe where they link to (for example, check the Nebari website).
[ ] This content adheres to the Nebari style guides.
Non-text content
[ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[ ] If there are emojis, there are not more than three in a row.
Reference Issues or PRs
What does this implement/fix?
Conda-store relies on PostgreSQL instance to run as part of its backend; currently, if not explicitly added to the
host_varsvariables, this will not be deployed by default. Which breaks the conda-store server servicePut a
xin the boxes that applyTesting
Documentation
Access-centered content checklist
Text styling
H1or#in markdown).Non-text content
Any other comments?