Updated the OCI Hook Injector README to resovle broken links to the p…

[swgriffith]

Resolves issue #33

Updates the links to podman documentation to reference the proper sha1 and adds additional details to help guide people in testing the hook-injector plugin, including relevant path details.

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: +0.16 🎉

Comparison is base (2a8b655) 63.83% compared to head (57cfa26) 64.00%.

❗ Current head 57cfa26 differs from pull request most recent head c783fc7. Consider uploading reports for the commit c783fc7 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
+ Coverage   63.83%   64.00%   +0.16%     
==========================================
  Files           9        9              
  Lines        1800     1800              
==========================================
+ Hits         1149     1152       +3     
+ Misses        500      497       -3     
  Partials      151      151              

see 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[klihub]

Looks good to me. Thanks for the fixes !

[kad]

Maybe it would be more sense to point to top of the tree like https://github.com/containers/common/tree/main/pkg/hooks and https://github.com/containers/common/blob/main/pkg/hooks/docs/oci-hooks.5.md instead of some older commit id in podman repo?

[klihub]

Maybe it would be more sense to point to top of the tree like https://github.com/containers/common/tree/main/pkg/hooks and https://github.com/containers/common/blob/main/pkg/hooks/docs/oci-hooks.5.md instead of some older commit id in podman repo?

We deliberately chose to point to the exact version we use in the plugin. That is then a different story that we should really file another PR to update the plugin to use a recent version, and then (remember to) update the link in the same PR as well.

[swgriffith]

@klihub and @kad - It sounds like we're leaving it as is. Let me know if you need me to change the URLs.

[kad]

I'm ok with @klihub opinion, so lgtm.

[mikebrow]

/LGTM thanks!