-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Skaffold init
supports Python projects with Buildpacks
#4309
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4309 +/- ##
=======================================
Coverage 71.95% 71.96%
=======================================
Files 323 323
Lines 12395 12404 +9
=======================================
+ Hits 8919 8926 +7
- Misses 2912 2913 +1
- Partials 564 565 +1
Continue to review full report at Codecov.
|
ping @nkubala @briandealwis |
artifacts: | ||
- image: skaffold-buildpacks | ||
buildpacks: | ||
builder: "gcr.io/buildpacks/builder" |
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.
In light of #4313, this should be with :v1
case file == "requirements.txt": | ||
if _, err := os.Stat(filepath.Join(filepath.Dir(path), "Procfile")); err == nil { | ||
valid = true | ||
} |
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.
The boolean return doesn't quite capture enough. We should be able to return output a message here along the lines of "...$path seems to be a Python project, but Buildpacks requires a Procfile". Or maybe this framework needs the ability to register a follow-up action (REQUIRES_PROCFILE
) so that the CLI/UI/IDE can offer the user some detail as to why it failed.
A todo for now is fine.
Signed-off-by: David Gageot <[email protected]>
864e692
to
5187bdd
Compare
Signed-off-by: David Gageot [email protected]