Terraform plan output for databases service

# Terraform plan output for databases service ## Progression ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/progression$ aws-env --profile sumdog-developer 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. module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_instance.replica: Refreshing state... module.system_check_autorecovery_replica.data.aws_partition.current: Refreshing state... data.aws_instance.database: Refreshing state... data.aws_vpc.current: Refreshing state... module.system_check_autorecovery_replica.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-03537921c54a9c6a1-SystemCheck-AutoRecovery-vpc-33f29b56] module.system_check_autorecovery_database.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-84a4c40d-SystemCheck-AutoRecovery-vpc-33f29b56] ------------------------------------------------------------------------ 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. ``` ## Cmaths ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/cmaths$ aws-env --profile sumdog-developer 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. module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_vpc.current: Refreshing state... data.aws_instance.database: Refreshing state... module.system_check_autorecovery_database.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-315572b4-SystemCheck-AutoRecovery-vpc-33f29b56] ------------------------------------------------------------------------ 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. ``` ## Questions: ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/questions$ aws-env --profile sumdog-developer 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. module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_instance.database: Refreshing state... data.aws_vpc.current: Refreshing state... module.system_check_autorecovery_database.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-05584470c3bbed25e-SystemCheck-AutoRecovery-vpc-33f29b56] ------------------------------------------------------------------------ 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. ``` ## Reports: ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/reports$ aws-env --profile sumdog-developer 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. data.terraform_remote_state.archives: Refreshing state... module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_vpc.current: Refreshing state... data.aws_instance.database: Refreshing state... aws_iam_role_policy_attachment.db_reports_archive_rw: Refreshing state... [id=dbReports-20190425145124259400000001] module.system_check_autorecovery_database.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-0c3c2c65e70817471-SystemCheck-AutoRecovery-vpc-33f29b56] ------------------------------------------------------------------------ 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. ``` ## Skills: ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/skills$ aws-env --profile sumdog-developer 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. module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_vpc.current: Refreshing state... data.aws_instance.database: Refreshing state... module.system_check_autorecovery_database.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-e2a5806b-SystemCheck-AutoRecovery-vpc-33f29b56] ------------------------------------------------------------------------ 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. ``` ## World: ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/world$ aws-env --profile sumdog-developer 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. data.aws_vpc.current: Refreshing state... module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_instance.database: Refreshing state... module.system_check_autorecovery_database.aws_cloudwatch_metric_alarm.auto_recovery_alarm[0]: Refreshing state... [id=i-0842a83671a447514-SystemCheck-AutoRecovery-vpc-33f29b56] ------------------------------------------------------------------------ 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. ``` ## Writting: Database Writting(prod-db-writing-1) do not exist on AWS That is why we get following error: ```bash= ~/projects/sumdog/foundational-infrastructure/terraform/databases/writing$ aws-env --profile sumdog-developer terraform plan [aws-env] Assuming role arn:aws:iam::307275847480:role/developers-20190122140127325800000001 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. module.system_check_autorecovery_database.data.aws_partition.current: Refreshing state... data.aws_vpc.current: Refreshing state... data.aws_instance.database: Refreshing state... Error: Your query returned no results. Please change your search criteria and try again. on remote_inputs.tf line 1, in data "aws_instance" "database": 1: data "aws_instance" "database" { ```