Repository navigation
Allow user to specify artifact name #44
Description
Activity
- changed the title
[-]Allow customer to specify artifact name[/-][+]Allow user to specify artifact name[/+]on Mar 7, 2024 Hey Igor Rodionov (@goruha) If you'd like I could propose a pull request for this 😉
TheBatman09, thanks for the feature request.
Your PR is more than welcome.Reacted by TheBatman09Voila !
Hi TheBatman09,
Thank you for bringing this up! Your use case makes sense, and I can see how the current hashing mechanism could cause conflicts when trying to store the same data twice with different step names.
I could say about some solutions in my mind:
- Allow users to specify a custom artifact name – This would give more control over naming and avoid hash-based conflicts.
- Include the step name in the hash calculation – This would differentiate artifacts even if their contents are identical.
- Provide an option to append a unique identifier (e.g., timestamp or UUID) – This would ensure uniqueness without requiring significant changes.
Hey thanks for your answer, actually I forked to be able to use it back in the days and I did made a pr with solution 1 : https://github.com/cloudposse/github-action-matrix-outputs-write/pull/45/files
Metadata
Metadata
Assignees
Labels
No labels
Use Case
Hello guys, I've started using this action and I came across the following issue: I have some dynamically retrieved data that I write with a step name and a matrix name. Then I retrieve some data again and try to write it with a different step name but same matrix name. And here when the data is the same for first and second time I get an error saying the artifact already exists. By looking at the code it looks like that's because the artifact name used is a hash of the content and in my case the content is the same in both cases.
Expected Behavior
I expect to be able to write the same data twice with a different step name.
Describe Ideal Solution
I think the ideal solution would be to add a parameter to the action to allow the user to chose the key used to store the artifact and/or also include the step name in the hash to allow storing twice the same data if it has a different step name.
Bonus
It seems like a fairly easy fix, i'd be happy to contribute if needed