mirror of https://github.com/databricks/cli.git
This commit is contained in:
parent
5b6ffd57bf
commit
963022af0f
|
@ -1,53 +1,3 @@
|
||||||
|
script: line 75: syntax error near unexpected token `|'
|
||||||
|
|
||||||
>>> $TERRAFORM init -no-color -get=false
|
Exit code: 2
|
||||||
|
|
||||||
Initializing the backend...
|
|
||||||
|
|
||||||
Initializing provider plugins...
|
|
||||||
- Finding databricks/databricks versions matching "1.64.1"...
|
|
||||||
- Installing databricks/databricks v1.64.1...
|
|
||||||
- Installed databricks/databricks v1.64.1 (unauthenticated)
|
|
||||||
|
|
||||||
Terraform has created a lock file .terraform.lock.hcl to record the provider
|
|
||||||
selections it made above. Include this file in your version control repository
|
|
||||||
so that Terraform can guarantee to make the same selections by default when
|
|
||||||
you run "terraform init" in the future.
|
|
||||||
|
|
||||||
|
|
||||||
Warning: Incomplete lock file information for providers
|
|
||||||
|
|
||||||
Due to your customized provider installation methods, Terraform was forced to
|
|
||||||
calculate lock file checksums locally for the following providers:
|
|
||||||
- databricks/databricks
|
|
||||||
|
|
||||||
darwin_arm64, so Terraform running on another platform will fail to install
|
|
||||||
these providers.
|
|
||||||
|
|
||||||
To calculate additional checksums for another platform, run:
|
|
||||||
terraform providers lock -platform=linux_amd64
|
|
||||||
(where linux_amd64 is the platform to generate)
|
|
||||||
|
|
||||||
Terraform has been successfully initialized!
|
|
||||||
|
|
||||||
You may now begin working with Terraform. Try running "terraform plan" to see
|
|
||||||
any changes that are required for your infrastructure. All Terraform commands
|
|
||||||
should now work.
|
|
||||||
|
|
||||||
If you ever set or change modules or backend configuration for Terraform,
|
|
||||||
rerun this command to reinitialize your working directory. If you forget, other
|
|
||||||
commands will detect it and remind you to do so if necessary.
|
|
||||||
|
|
||||||
>>> $TERRAFORM plan -no-color
|
|
||||||
data.databricks_current_user.me: Reading...
|
|
||||||
data.databricks_current_user.me: Read complete after (redacted) [id=$USER.Id]
|
|
||||||
|
|
||||||
Changes to Outputs:
|
|
||||||
+ username = "$USERNAME"
|
|
||||||
|
|
||||||
You can apply this plan to save these new output values to the Terraform
|
|
||||||
state, without changing any real infrastructure.
|
|
||||||
|
|
||||||
─────────────────────────────────────────────────────────────────────────────
|
|
||||||
|
|
||||||
Note: You didn't use the -out option to save this plan, so Terraform can't
|
|
||||||
guarantee to take exactly these actions if you run "terraform apply" now.
|
|
||||||
|
|
|
@ -9,6 +9,6 @@
|
||||||
# so Terraform running on another platform will fail to install these
|
# so Terraform running on another platform will fail to install these
|
||||||
# providers.
|
# providers.
|
||||||
|
|
||||||
trace $TERRAFORM init -no-color -get=false | grep -v 'includes checksums for'
|
trace $TERRAFORM init -no-color -get=false | grep -v 'includes checksums for' | | grep -v 'so Terraform running on another' | grep -v 'providers\.'
|
||||||
trace $TERRAFORM plan -no-color
|
trace $TERRAFORM plan -no-color
|
||||||
rm -fr .terraform.lock.hcl .terraform
|
rm -fr .terraform.lock.hcl .terraform
|
||||||
|
|
Loading…
Reference in New Issue