Deploy

[jcahail]

No description provided.

[KlaasH]

Extra deployment steps:

• Remove batch_tilemaker_job_queue_name and use_tilegarden variables from the tfvars file (Remove tilemaker #720)
• Adjust config files for Define Tilegarden executor role in Terraform config #719 and Add Terraform var for Tilegarden function name #729:
  • Add tilegarden_function_name = "pfbTilegardenProduction" to the tfvars file
  • In the Tilegarden .env file, change the PROJECT_NAME variable to LAMBDA_FUNCTION_NAME (the value should remain pfbTilegardenProduction) and remove the LAMBDA_ROLE variable.
  • Change the executor name in claudia.json to match the one created by Terraform (pfbTilegardenProductionExecutor).
  • Redeploying might not actually change the role, so check in the Lambda console and change it manually to the new role if necessary.
• Run migrations. There are two:
  • Removing Tilemaker-related fields (Remove tilemaker #720)
  • Converting territories to states (Treat territories as states; show country in label #725)
  • Since one is dropping fields and the other is a data migration, there's no need to try to get them applied before the new app tasks spin up. In fact, the migrated schema will be incompatible with the old code, so we should wait until the service has fully updated to apply the migrations.

[KlaasH]

Version 0.9.2 deployed.

US Territories are now treated as states, and non-US cities will include their country name in their label.

There was an old San Juan neighborhood (from 2018), with 2 failed jobs, that already had state=PR and country=US. I think it must have been imported that way as part of a batch. It was blocking the migration, since there's a uniqueness constraint on (name, state, country, organization), so I removed it.