GoogleContainerTools/skaffold

Document requirements for skaffold init --analyze to detect buildpack entrypoint for Python

Open

#4,377 opened on Jun 23, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (1,416 forks)batch import
area/docsbuild/buildpackshelp wantedkind/documentationpriority/p2

Repository metrics

Stars
 (12,822 stars)
PR merge metrics
 (Avg merge 3d 6h) (16 merged PRs in 30d)

Description

Expected behavior

Cloud Code python samples (k8s and Cloud Run) do not work out of the box with skaffold buildpack builders, and it is unclear how a python project needs to be architected to cause skaffold to detect buildpacks as a builder.

It looks like this is a more general GCP buildpacks issue as well. https://github.com/GoogleCloudPlatform/buildpacks/issues/45

Information

  • Skaffold version: version e03e4d8
  • Operating system: macOS 10.15.4

Contributor guide

Research direction
Read the current skaffold init analyze documentation for buildpack detection and look at the Cloud Code Python samples to understand what is missing.
Tech stack
go
Domain
devops
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85