Why env0
Solutions
Infrastructure as Code (IaC) Automation Teams and GovernanceManaged Self-Service env0 for the Enterprise
DocumentationPricing
Resources
Case StudiesIn the NewsVideosWebinars
Blog
Login
Get a Demo
FREE TRIALContact us
Dec 20, 2021

Module Registry and Terraform Provider Updates

Sean O'Dell
Director of Product Marketing and Developer Relations

Module Registry and Terraform Provider Updates 

Depending upon where you began your journey into Infrastructure as Code and Hashicorp Terraform, one of the most obvious features is the module registry. It really wasn’t anything talked about other than it was “there” thanks to the Terraform Registry. While I personally utilize the public registry on a regular basis, it became very clear over time that I had a need for a private Module Registry, too. Our fantastic customers and partners (and even our dev teams here) also began asking for the same thing. We are excited to deliver this highly requested feature.


The image above includes a few private modules focused on AWS EKS Cluster creation and management that Andrew Way, Sales Engineer at env0 built because of organizational goals and objectives. 

As usual, our desire is for the community to consume these new features in a way that makes sense to you just in case the blog format is not your preference.

  • env0 docs - env0 Module Registry
  • Video from Andrew Way

env0 Module Registry

The env0 Module Registry is a private registry for Terraform modules, allowing you to privately share and reuse Terraform modules within your organization.

 


Module Creation

To create a new module, the team created a simple wizard to help guide you through the process.

Required Details

  • Name - this can be any string of your choice, for example, eks or gke.
  • Provider - this can also be any string of your choice, for example, aws or gcp.
  • Description - A useful way of summarizing what the module does and when it should be use.

NOTE: The combination of name and provider must be unique within your organization’s modules.

VCS Provider

 VCS provider you’d like to use, and after you’ve authorized env0 to access your repositories, select a repository from the dropdown. It is assumed your module’s code is stored in the root folder of the repository.

NOTE: Each module requires its own separate repository.  i.e. The module registry currently does not support mono-repos of modules.

Module Versioning

Versioning is a common concept within Terraform and the same principles apply for our Module Registry.

  • ‍Semantic versioning format (e.g. 1.0.0)
  • Versions must be applied to your source repository as git tags.

There are a few ways to utilize these modules depending upon your use case:

  • Using a module in your code
  • Using a module locally

Module List

The Modules List page is available to every user in the organization by clicking on “Module Registry” in the organization’s menu.

You can use the search box to locate specific modules by name, provider, description, or the users who created them.

Module Page

On this page you can see the details of your Module.

  • Versions dropdown - versions are linked to Git tags in your repository, which match the semantic versioning schema
  • Readme tab - will show the contents of the README.md in your repository.
  • Instructions tab - will include instructions on how the module can be used in your Terraform code.

env0 Terraform Provider

Would an Infrastructure as Code Management Platform be usable if it didn’t have it’s own Terraform Provider? I don’t think so! The team at env0 has built a Terraform Provider to help you manage your env0 via Configuration as Code.

I won’t be covering the “How To” in this blog because the documentation does a better job due to the schematic requirements and layout that we are all accustomed to on the Terraform Provider site. Check it out for yourself here.

Based upon feedback from our customers, the following three resources make the most sense:

  • ‍Project‍
  • Templates‍
  • Environments

Included with each resource is what the resulting output would look like from within the env0 UI.

Projects are used in env0 to provide granular access control to Environments. Every environment in env0 exists under a project, and users are given access on a per-project basis.

 Templates in env0 defines a type of environment that can be deployed

Environments in env0 is an entity representing a deployment managed by env0.


These new enhancements and features are driven by our end users and we are always looking for feedback. Feel free to reach out and let us know what you think and what else you want to see in these areas.

Interested in learning more about env0?
Request a Demo
SHARE
You may also like
Recommendations for Migrating from Terraform Cloud
Infrastructure as Code is a Creative Job
How to integrate Azure DevOps with env0
Go back to blog
CNCF Member Badge
Company
About UsIn the NewsPress ReleasesCase StudiesAdditional ResourcesCareers
Developer and DevOps
APITerraform ProviderTerratag Open Source
Terraform Cloud AlternativeDIY AlternativeAtlantis Alternative
FREE TRIAL
Follow Us
Terms of ServicePrivacy PolicySecuritySystem Status
© Copyright env0 2023
This website uses cookies. We use cookies to ensure that we give you the best experience on our website. Learn More
PreferencesDenyAccept
Privacy Preference Center
When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website.
Reject all cookiesAllow all cookies
Manage Consent Preferences by Category
Essential
Always Active
These items are required to enable basic website functionality.
Marketing
These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission.
Personalization
These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location.
Analytics
These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor.
Confirm my preferences and close