opentofu/terraform/version.go

package terraform

import (
	"github.com/hashicorp/terraform/version"
)

// TODO: update providers to use the version package directly
func VersionString() string {
	return version.String()
}
Expose Terraform version internally & externally 2015-06-21 06:19:24 -05:00			`package terraform`

core: Add terraform_version to state This adds a field terraform_version to the state that represents the Terraform version that wrote that state. If Terraform encounters a state written by a future version, it will error. You must use at least the version that wrote that state. Internally we have fields to override this behavior (StateFutureAllowed), but I chose not to expose them as CLI flags, since the user can just modify the state directly. This is tricky, but should be tricky to represent the horrible disaster that can happen by enabling it. We didn't have to bump the state format version since the absense of the field means it was written by version "0.0.0" which will always be older. In effect though this change will always apply to version 2 of the state since it appears in 0.7 which bumped the version for other purposes. 2016-03-11 13:07:54 -06:00			`import (`
use the new version package Update all references to the version values to use the new package. The VersionString function was left in the terraform package specifically for the aws provider, which is vendored. We can remove that last call once the provider is updated. 2017-10-19 20:48:08 -05:00			`"github.com/hashicorp/terraform/version"`
core: Add terraform_version to state This adds a field terraform_version to the state that represents the Terraform version that wrote that state. If Terraform encounters a state written by a future version, it will error. You must use at least the version that wrote that state. Internally we have fields to override this behavior (StateFutureAllowed), but I chose not to expose them as CLI flags, since the user can just modify the state directly. This is tricky, but should be tricky to represent the horrible disaster that can happen by enabling it. We didn't have to bump the state format version since the absense of the field means it was written by version "0.0.0" which will always be older. In effect though this change will always apply to version 2 of the state since it appears in 0.7 which bumped the version for other purposes. 2016-03-11 13:07:54 -06:00			`)`

use the new version package Update all references to the version values to use the new package. The VersionString function was left in the terraform package specifically for the aws provider, which is vendored. We can remove that last call once the provider is updated. 2017-10-19 20:48:08 -05:00			`// TODO: update providers to use the version package directly`
Add VersionString We conditionally format version with VersionPrerelease in a number of places. Add a package-level function where we can unify the version format. Replace most of version formatting in terraform, but leave th few instances set from the top-level package to make sure we don't break anything before release. 2016-07-21 13:07:16 -05:00			`func VersionString() string {`
use the new version package Update all references to the version values to use the new package. The VersionString function was left in the terraform package specifically for the aws provider, which is vendored. We can remove that last call once the provider is updated. 2017-10-19 20:48:08 -05:00			`return version.String()`
Add VersionString We conditionally format version with VersionPrerelease in a number of places. Add a package-level function where we can unify the version format. Replace most of version formatting in terraform, but leave th few instances set from the top-level package to make sure we don't break anything before release. 2016-07-21 13:07:16 -05:00			`}`