Skip to content

Remove ENV requirement for db migration #654

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Oct 31, 2024
Merged

Conversation

dmchoiboi
Copy link
Collaborator

Pull Request Summary

What is this PR changing? Why is this change being made? Any caveats you'd like to highlight? Link any relevant documents, links, or screenshots here if applicable.

This requirement is too strict. ENV is not a guaranteed environemntal variable

Test Plan and Usage Guide

How did you validate that your PR works correctly? How do you run or demo the code? Provide enough detail so a reviewer can reasonably reproduce the testing procedure. Paste example command line invocations if applicable.

Copy link
Contributor

@seanshi-scale seanshi-scale left a comment

Choose a reason for hiding this comment

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

think we just need infra_config().env to exist, which I guess is always true

@dmchoiboi dmchoiboi enabled auto-merge (squash) October 31, 2024 00:42
@dmchoiboi dmchoiboi merged commit 0024b0c into main Oct 31, 2024
7 checks passed
@dmchoiboi dmchoiboi deleted the dmchoi/remove-env branch October 31, 2024 00:55
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants