Closed richardhallett closed 11 months ago
Global
Prod-EU-West VPC
Stage VPC
Test VPC
Cleanup old dev setup from structure
These services vary between 0.11 to 0.12, they need to be upgraded in turn and ensure their state matches what is deployed.
Production services akita analytics analytics-api api assets bastion blog check-indexed-dois check-links cheetoh citation client-api content-negotiation crossref-agent crossref-orcid-agent crossref-related-agent datadog datafiles-generator - This is running but I think it is unused and wasting resources, upgrade but disable. delete-test-dois doi federation ftp - To delete homepage http-redirect levriero mds message-queue metrics-api oai pidcheck profiles raw-resolution-logs re3data repository-finder salesforce-api schema search sitemaps-generator stats-portal store-crawler-results strapi - This is cms.datacite.org - It only exists to update a list of service providers on homepage via url https://cms.datacite.org/service-providers
Stage services
akita analytics analytics-api api assets bastion blog - Needs tidying to remove old s3 buckets check-indexed-dois check-links cheetoh clickhouse-ebs client-api content-negotiation datafiles-generator - This is running but I think it is unused and wasting resources, upgrade but disable. delete-test-dois demorepo doi federation handle homepage - Needs tidying to remove old s3 buckets http-redirect levriero mds message-queue metrics-api oai pidcheck profiles re3data repository-finder resolution-logs-pipeline salesforce-api schema search sitemaps-generator slides stats-portal store-crawler-results strapi
assets cheetoh client-api doi handle http-redirect mds message-queue metrics-api
This needs investigating to ensure all AWS resources have configuration detailed in mastino. Careful attention needs to be paid to anything that maybe private. Some things are configured via old datacite/ops private repository.
Redefine github workflows to instead deploy task definitions from those defined in application code, making terraform code just infrastructure and not config management.
Additional note discovered during upgrade testing is we may need to do a process for upgrading the AWS provider version at the same time. See: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-4-upgrade https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-5-upgrade
Research how best to handle the upgrade process, there is existing documentation and thoughts on how this can be achieved. This issue is how best to proceed but also how to break down the work into manageable chunks.