load manifest form tar file

[hhstu]

Fixes #1032

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[jonjohnsonjr]

I agree we need this but I don't want the parameter to be a string, so that you can use this for in-memory tarballs. Can you make this take an Opener?

[hhstu]

get

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[codecov-commenter]

Codecov Report

Merging #1033 (1cd5b48) into main (4cdd086) will decrease coverage by 0.18%.
The diff coverage is 20.00%.

❗ Current head 1cd5b48 differs from pull request most recent head 02dacf6. Consider uploading reports for the commit 02dacf6 to get more accurate results

@@            Coverage Diff             @@
##             main    #1033      +/-   ##
==========================================
- Coverage   75.22%   75.03%   -0.19%     
==========================================
  Files         107      107              
  Lines        5053     5079      +26     
==========================================
+ Hits         3801     3811      +10     
- Misses        706      725      +19     
+ Partials      546      543       -3     

Impacted Files	Coverage Δ
pkg/crane/options.go	90.47% <0.00%> (-9.53%)	⬇️
pkg/gcrane/options.go	46.66% <0.00%> (-31.12%)	⬇️
pkg/v1/tarball/image.go	74.39% <0.00%> (-3.82%)	⬇️
pkg/v1/remote/write.go	63.59% <71.42%> (+0.63%)	⬆️
pkg/crane/catalog.go	100.00% <100.00%> (ø)
pkg/authn/keychain.go	100.00% <0.00%> (ø)
pkg/v1/remote/multi_write.go	58.95% <0.00%> (+2.98%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b535fa...02dacf6. Read the comment docs.

[jonjohnsonjr]

Thanks! Can you squash these commits and make sure they are both authored as hhstu for the CLA check?