JTAF is now version 0.1.2

[davedotdev]

• Major improvements to the way providers are created.

Provider code is now entirely copied to the working directory that is referenced in the config file. That means all of the .go code is in one place without copying indivial files.

• Commits are handled on terraform destroy

There is now a new commit resource called destroycommit which has inverse logic; it commits on a Terraform delete instead of create. This means that when a Terraform module makes use of it, the commit is automatically applied when the resources are destroyed.

• There is now a full example including terraform module best practice sample in the samples directory.

This is our best practice approach.

• The Wiki on the GitHub page is updated. Once this PR is merged, I'll finish the build example steps.

• The go.mod is magically populated into the terraform_providers working directory identified in the config file.

• Testing now with Terraform 0.15.5 and the module 'depends_on' key, which gives us great flexibility.

• The providers generated can now be called other names other than 'junos-device'. For example, if you put the name 'vsrx' into the 'providerName' field in the config file, the provider will be called junos-vsrx and when the Go code is compiled, the provider will be called terraform-provider-junos-vsrx

• When destroying resources, the driver calls are now without a commit where previously a commit was attempted for every resource removal. The commit requirement is a part of the terraform input file process now instead of in code. We can't infer when to apply commit through some CRUD actions, so it was an inefficient way of doing this task.

[davedotdev]

Dealt with the conversion of qfx_1 to vsrx_1 in all locations (pushed to the latest commit on this branch.

Regarding the YANG files - the idea here is that everything is included to run a successful demo. The file overhead is minimal and users can concentrate on JTAF itself.