-
Notifications
You must be signed in to change notification settings - Fork 239
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
fix: better elixir docs and defaults #1207
Conversation
This pull request is stale because it has been open 10 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Friendly reminder regarding this pull request! Please let me know if there are any further updates needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Sorry its taken so long to get to and review.
I've updated the snapshot tests for elixir that was failing the build. Just one comment about the ecto.setup being removed, but besides that, it looks good to go.
@@ -51,9 +45,6 @@ impl Provider for ElixirProvider { | |||
build_phase.add_cmd("mix assets.deploy".to_string()); | |||
} | |||
|
|||
if mix_exs_content.contains("postgrex") && mix_exs_content.contains("ecto") { | |||
build_phase.add_cmd("mix ecto.setup"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, for me I didn't want this. Will add it back in.
The risk with running ecto.setup is it generally requires a DB connection, which is not available when the image is being built.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah thats no worries then. I'll merge as is but I wonder if we can detect if ecto setup is needed/will work
Two main improvements:
I don't think additional tests are needed here. Refactored to pattern off of the python provider a bit more closely.