ArnoSen
ArnoSen
I can confirm this. I have no problem with creating a PR for this but then the desired behavior needs to be clear. IMHO there are 2 use cases that...
I have experience with creating the json that Terralist requires for new versions manually. The next step for me would be to automate this. I think that creating a bash...
I did not know that jq could be used for generating json files so I am giving it a try. My preference is to have the different architectures dynamically added...
Hi @valentindeaconu, I hope this helps: ``` [ { "name": "terraform-provider-example_v0.0.3", "path": "/mypath/terraform-provider-example/dist/terraform-provider-example_linux_amd64_v1/terraform-provider-example_v0.0.3", "goos": "linux", "goarch": "amd64", "goamd64": "v1", "internal_type": 4, "type": "Binary", "extra": { "Binary": "terraform-provider-example_v0.0.3", "Ext": "", "ID":...
Also interesting is maybe: https://github.com/orgs/goreleaser/discussions/3750
You can think of an alternative scenario where you allow the the user to also submit a download URL when they submit the artifacts object. For example: POST /v1/terralist/createVerion?baseURL=https://mysite/downloads/terraform/ Then...
Sounds good! I rechecked my script and the only thing I can see missing is the Terraform protocol versions. Maybe that should be a request param as well?
'trying to implement' does not sound that nice. For me it is a hard requirement is that the architectures are dynamically detected from the artifacts.json file. This adds some complexity...
Thanks for reconsidering. I hope I was not too bold. If it happened , it was not my intention. I am happy to contribute. Also I am quite busy lately...