This is more of a question than an issue, but we currently have a github release in which the artifacts for a certain platform have the same name across versions, for example: ytt-darwin-amd64. This is causing errors when trying to automate the release creation with this resource because of duplicate filenames, although this is permitted via the UI. It looks like the browser uses the https://network.pivotal.io/rails/active_storage/direct_uploads endpoint which provides a key and upload url whereas this resource computes a key locally and constructs the upload URL itself. Is there a specific reason this resource doesn't allow the same behavior that the UI does?
Thanks!
Eli
Note: we are more than willing to update our releases to include version numbers to distinguish them.
This is more of a question than an issue, but we currently have a github release in which the artifacts for a certain platform have the same name across versions, for example:
ytt-darwin-amd64
. This is causing errors when trying to automate the release creation with this resource because of duplicate filenames, although this is permitted via the UI. It looks like the browser uses thehttps://network.pivotal.io/rails/active_storage/direct_uploads
endpoint which provides a key and upload url whereas this resource computes a key locally and constructs the upload URL itself. Is there a specific reason this resource doesn't allow the same behavior that the UI does?Thanks! Eli
Note: we are more than willing to update our releases to include version numbers to distinguish them.