Skip to content
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

Lifecycle only gets remote or local image, without concern for pulling #91

Merged
merged 5 commits into from
Mar 11, 2019

Conversation

thisisnotashwin
Copy link
Member

@thisisnotashwin thisisnotashwin commented Mar 5, 2019

  • Lifecycle farms out responsibility of pulling to pack
  • We want to ensure that pack does not return an error in the
    situation where we can pull from remote but the image only exists
    locally

[buildpacks/pack#90]

@thisisnotashwin thisisnotashwin requested a review from sclevine March 5, 2019 23:00
@ekcasey
Copy link
Member

ekcasey commented Mar 6, 2019

@ashwin-venkatesh @joaopapereira

I wonder if it makes sense to take the pulling logic out of NewLocal and move it into pack. The lifecycle binaries never actually pull images.

I'm thinking about the pull logs and this upcoming bug buildpacks/roadmap#49, both of which would be less complicated if the pull logic lived in pack

Additionally I'm worried that pack might print confusing logs if it can't determine whether the image was pulled or not.

image/local.go Outdated Show resolved Hide resolved
image/local.go Outdated Show resolved Hide resolved
image/local_test.go Outdated Show resolved Hide resolved
image/local_test.go Outdated Show resolved Hide resolved
image/local_test.go Outdated Show resolved Hide resolved
image/local_test.go Outdated Show resolved Hide resolved
@ameyer-pivotal ameyer-pivotal requested a review from sclevine March 11, 2019 15:55
@ameyer-pivotal ameyer-pivotal changed the title Check local registry for image if image not available in remote Lifecycle only gets remote or local image, without concern for pulling Mar 11, 2019
image/local.go Outdated Show resolved Hide resolved
image/local.go Outdated Show resolved Hide resolved
Ashwin Venkatesh and others added 4 commits March 11, 2019 11:41
- We want to ensure that lifecycle does not return an error in the
  situation where we can pull from remote but the image only exists
locally

[buildpacks/pack#90]

Signed-off-by: Joao Pereira <[email protected]>
Signed-off-by: Ashwin Venkatesh <[email protected]>
Signed-off-by: Andrew Meyer <[email protected]>
Signed-off-by: Joao Pereira <[email protected]>
Signed-off-by: Andrew Meyer <[email protected]>
Signed-off-by: Andrew Meyer <[email protected]>
Signed-off-by: Andrew Meyer <[email protected]>
@ameyer-pivotal ameyer-pivotal dismissed sclevine’s stale review March 11, 2019 16:43

Issues addressed or outdated. Please take another look now.

@ameyer-pivotal ameyer-pivotal requested review from ameyer-pivotal and removed request for ameyer-pivotal March 11, 2019 16:44
Signed-off-by: Andrew Meyer <[email protected]>
@ameyer-pivotal ameyer-pivotal merged commit 959c946 into master Mar 11, 2019
@ameyer-pivotal ameyer-pivotal deleted the fix-issue-pack90 branch March 11, 2019 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants