Version and release your module on Terraform Cloud - Getting started with Terraform (Part 3)
HTML-код
- Опубликовано: 6 сен 2024
- #terraform #devops #infrastructureascode
Now that we have a module, we want to version it to allow updates and letting downstream consumers decided when to update. In this episode, we add versioning and also release our module on Terraform Cloud.
If you have any questions about this video, or suggestions for content I should cover next, please leave a comment, or reach out to me on social media, details are down below.
Pull up a 🪑and bring a ☕/ 🍵/ 🍸/ 🍺, this channel focusses on Cloud related tech, mostly AWS, with practical, hands-on guides. New videos posted weekly (soon). If you have questions / suggestions for content, please leave a comment on any of the videos.
AWS Technical Developer Advocate, focussing on DevOps ❤️, containers 📦 and a bit of security🔐. Opinions are mine.
COME CHAT:
Twitter: bit.ly/cobus-t...
LinkedIn: bit.ly/cobus-l...
Instagram: bit.ly/cobus-i...
Facebook: bit.ly/cobus-f...
I have learned so much from these series.
On Windows, the terraformrc file must be named terraform.rc and placed in the relevant user's %APPDATA% directory. The physical location of this directory depends on your Windows version and system configuration; use $env:APPDATA in PowerShell to find its location on your system.
In my case I have created terraform.rc file in \AppData\Roaming and its working
Cobus you rock!!
Your terraform videos are very clean and perfect, thanks for the great work!
Hello. thank you for that video, it s clear / precise / easy to understand / usefull. One thing tough: you should add it to your youtube "terraform playlist"....
Thanks for sharing
Can we do the same in Gitlab? Do you have a full course ?
Liked it very much. However, would be nice to know how we can restrict or manually approve the module to be published rather not synced everytime a new tagging is made to the module repo?
We need more videos!!!
how about when we host our modules in a private git hub repo, how will the authentication work ?
thanks for a greate video. in the video you show with 1 repo with 1 module . Is there a way to deal with 1 repo that holds many modules ? (in my case I have 1 dedicated repo for my "tf-modules" and another repo with my env's e.g. production / stg / dev that calling different modules from "tf-modules") - thanks !
appriciate your answer here
Thx mate