Version Control

There is no version control built into the providers that JTAF creates, which creates an issue in so much as tracking what you've created and where to put it. Fear not!

Use the Terraform native way of version control and our semantic version numbering to help you maintain a version number.

Using the example provider that can be created using the assets in the samples/tf_module_template directory, let's dive into version numbers.

.terraform.d
├── checkpoint_cache
├── checkpoint_signature
└── plugins
    └── juniper
        └── providers
            └── junos-vsrx
                └── 20.32.101
                    ├── darwin_amd64
                    │   └── terraform-provider-junos-vsrx
                    └── linux_amd64

Note the 20.32.101 version.

This represents a vSRX 20.3R2.1 software release with a Terraform provider build of 01. The Terraform provider build number is only significant either to Juniper (if it's a public provider) or to you, if you've created one. Our advice is to create an md5 hash of the providers you build and somewhere create a spreadsheet or CMDB entry with the hash, the version number, the name and contents.

Because each provider can have almost entirely different contents, it's imperative you track this information.