You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found an issue with the 0.0.7 version:
If you run a command passing as argument a string that the first characters matches the command name, terraform will accept it:
$ terraform version
Terraform v0.7.0
$ terraform planXXXXXX
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but
will not be persisted to local or remote state storage.
data.terraform_remote_state.elasticache-subnet-groups: Refreshing state...
No changes. Infrastructure is up-to-date. This means that Terraform
could not detect any differences between your configuration and
the real physical resources that exist. As a result, Terraform
doesn't need to do anything.
~/dev/automation/terraform/teste (BTW-23)$
This behavior does not happen on version 0.6.x:
~ $ terraform --version
Terraform v0.6.16
Your version of Terraform is out of date! The latest version
is 0.7.0. You can update by downloading from www.terraform.io
~ $ terraform plan
Error loading config: No Terraform configuration files found in directory: /Users/Developer
~ $ terraform plansdfsdf
usage: terraform [--version] [--help] <command> [<args>]
Available commands are:
apply Builds or changes infrastructure
destroy Destroy Terraform-managed infrastructure
fmt Rewrites config files to canonical format
get Download and install modules for the configuration
graph Create a visual graph of Terraform resources
init Initializes Terraform configuration from a module
output Read an output from a state file
plan Generate and show an execution plan
push Upload this Terraform module to Atlas to run
refresh Update local state file against real resources
remote Configure remote state storage
show Inspect Terraform state or plan
taint Manually mark a resource for recreation
untaint Manually unmark a resource as tainted
validate Validates the Terraform files
version Prints the Terraform version
~ $
PS: Tested only on OSX.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 23, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I've found an issue with the 0.0.7 version:
If you run a command passing as argument a string that the first characters matches the command name, terraform will accept it:
This behavior does not happen on version 0.6.x:
PS: Tested only on OSX.
The text was updated successfully, but these errors were encountered: