-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
http data source #11552
Comments
Thanks for opening up this feature request. This seems like a good datasource to have. I don't think this is something that we would be able to get to any time soon. But we will gladly review a PR if you were interested in adding the feature. I'm going to label this as a help-wanted issue in case other members of the community are also interested in help out. |
I can try to take a look at this |
@nywilken Created PR. Please let me know if I should change anything, looks like it's pending a vercel deployment. Thanks! |
@teddylear may i know if you are still working on this request? I really want to have this new feature as my packer script is waiting for it. |
Thank you @teddylear for the contribution! I wish I could've been more help, but I've never done golang before 😅 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Similar to Terraform's http data source, it would be handy to have an http data source inside of the HCL for packer.
Use Case(s)
Ideally you'd be able to query API endpionts and other things with it, allowing your HCL to dynamically change based on the API results.
My specific use case is I'd like to submit a template to bento project's CentOS Stream templates, and because they've had issues with things being more dynamic with the stream update it's been hard to have something consistently work. We already worked up stream once to try and get a more "official" solution, but it has broken again with the stream 9 build.
Potential configuration
same as the terraform one
Potential References
The text was updated successfully, but these errors were encountered: