Created
July 30, 2018 17:45
Revisions
-
Ryan C Koch created this gist
Jul 30, 2018 .There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,135 @@ ➜ terraform plan 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. ------------------------------------------------------------------------ An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: + google_project.project id: <computed> app_engine.#: "1" app_engine.0.auth_domain: <computed> app_engine.0.code_bucket: <computed> app_engine.0.default_bucket: <computed> app_engine.0.default_hostname: <computed> app_engine.0.feature_settings.#: "1" app_engine.0.feature_settings.0.split_health_checks: "false" app_engine.0.gcr_domain: <computed> app_engine.0.location_id: "us-east1" app_engine.0.name: <computed> app_engine.0.serving_status: <computed> app_engine.0.url_dispatch_rule.#: <computed> auto_create_network: "true" billing_account: "######-######-######" folder_id: <computed> name: "testproject" number: <computed> org_id: "############" policy_data: <computed> policy_etag: <computed> project_id: "testproject-11399" skip_delete: <computed> Plan: 1 to add, 0 to change, 0 to destroy. ------------------------------------------------------------------------ Note: You didn't specify an "-out" parameter to save this plan, so Terraform can't guarantee that exactly these actions will be performed if "terraform apply" is subsequently run. ➜ terraform apply -auto-approve google_project.project: Creating... app_engine.#: "" => "1" app_engine.0.auth_domain: "" => "<computed>" app_engine.0.code_bucket: "" => "<computed>" app_engine.0.default_bucket: "" => "<computed>" app_engine.0.default_hostname: "" => "<computed>" app_engine.0.feature_settings.#: "" => "1" app_engine.0.feature_settings.0.split_health_checks: "" => "false" app_engine.0.gcr_domain: "" => "<computed>" app_engine.0.location_id: "" => "us-east1" app_engine.0.name: "" => "<computed>" app_engine.0.serving_status: "" => "<computed>" app_engine.0.url_dispatch_rule.#: "" => "<computed>" auto_create_network: "" => "true" billing_account: "" => "######-######-######" folder_id: "" => "<computed>" name: "" => "testproject" number: "" => "<computed>" org_id: "" => "############" policy_data: "" => "<computed>" policy_etag: "" => "<computed>" project_id: "" => "testproject-11399" skip_delete: "" => "<computed>" google_project.project: Still creating... (10s elapsed) google_project.project: Still creating... (20s elapsed) google_project.project: Still creating... (30s elapsed) google_project.project: Still creating... (40s elapsed) google_project.project: Still creating... (50s elapsed) google_project.project: Creation complete after 51s (ID: testproject-11399) Apply complete! Resources: 1 added, 0 changed, 0 destroyed. ➜ tmp2 git:(ryanckoch/add-app-engine-support) ✗ terraform plan 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. google_project.project: Refreshing state... (ID: testproject-11399) ------------------------------------------------------------------------ An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: ~ google_project.project app_engine.0.feature_settings.0.split_health_checks: "true" => "false" Plan: 0 to add, 1 to change, 0 to destroy. ------------------------------------------------------------------------ Note: You didn't specify an "-out" parameter to save this plan, so Terraform can't guarantee that exactly these actions will be performed if "terraform apply" is subsequently run. ➜ terraform apply -auto-approve google_project.project: Refreshing state... (ID: testproject-11399) google_project.project: Modifying... (ID: testproject-11399) app_engine.0.feature_settings.0.split_health_checks: "true" => "false" google_project.project: Still modifying... (ID: testproject-11399, 10s elapsed) google_project.project: Modifications complete after 12s (ID: testproject-11399) Apply complete! Resources: 0 added, 1 changed, 0 destroyed. ➜ terraform plan 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. google_project.project: Refreshing state... (ID: testproject-11399) ------------------------------------------------------------------------ No changes. Infrastructure is up-to-date. This means that Terraform did not detect any differences between your configuration and real physical resources that exist. As a result, no actions need to be performed.