-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Provide 'Releases' data source #144
Comments
Hi @kheldar Do you mind providing a bit more context about your use case? Specifically I'm curious which Terraform provider & resource would you use to deploy the artefact. |
In this specific instance, I need to get it onto S3 (the artefact is a Lambda package). In general, it would be good to be able to pass this to any resource that can currently take a file. That said, even being able to get a resolvable URL would be a pretty decent start. |
Bumping this and also providing another use case. We would like to get version numbers from a github release (or tag, but that is a different API and therefore probably a different data source from this card) that would then be used to deploy that version of a docker container with another terraform provider. (AWS in our case but could be anything else) |
Hi, I'd like to work on this if possible? I notice it's an older ticket but believe there is still some value in providing this data source? |
GH-144 - New Data Source: Github release
…releases-data-source integrationsGH-144 - New Data Source: Github release
👋 Hey Friends, this issue has been automatically marked as |
Closing this as #144 has been merged and released already. Please feel free to open up new issues for any problems that may crop up! |
I would find it useful to be able to retrieve release artefacts from GitHub via Terraform (i.e. the data that can technically be gotten from https://api.github.com/repos/:owner/:repo/releases and its sub-APIs at the moment).
For context, I need to grab a release artefact that's being published to a private GitHub and deploy it to our infrastructure. The fact that it's private means that I can't just point TF at the public HTTPS endpoint for the artefact, and interacting with the API itself is complex enough it would require scripting.
The text was updated successfully, but these errors were encountered: