Works great! Thanks!

I'm a bit worried about the ambiguity here. Would be very surprising if a secret value would ever collide with a path. Could we somehow make it clear that the user expects the value to be a path?

@tonistiigi My suggestions in #293 were a new action input (secret-files: npmrc=path/to/file) or a special syntax in the secrets input that could be intermixed with string secrets (secrets: file:npmrc=path/to/file). What do you think?

@ngraef SGTM, secrets: file:npmrc=path/to/file is still at least theoretically ambiguous as : could be part of the ID as well.

@tonistiigi @ngraef

I'm a bit worried about the ambiguity here. Would be very surprising if a secret value would ever collide with a path. Could we somehow make it clear that the user expects the value to be a path?

A new input SGTM.

Codecov Report

Merging #296 (33eec15) into master (e5f26cd) will increase coverage by 0.04%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master     #296      +/-   ##
==========================================
+ Coverage   74.34%   74.39%   +0.04%     
==========================================
  Files           4        4              
  Lines         152      164      +12     
  Branches       26       28       +2     
==========================================
+ Hits          113      122       +9     
- Misses         21       22       +1     
- Partials       18       20       +2     

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 e5f26cd...33eec15. Read the comment docs.

@tonistiigi @ngraef secret-files input has been added. Let me know if it looks good to you (can be tested with crazy-max/docker-build-push-action@secret-file).

Just tested. secret-files works for me.