upgrade airbyte to 0.58.0

[Ishankoradia]

Topic

No response

Relevant information

No response

[Ishankoradia]

• stop all pm2 processe
• stopped airbyte using docker compose down
• upated the version in run-ab-platform.sh to 0.58.0
• ran ./run-ab-platform.sh -r and then ./run-ab-platforn.sh -d. This downloaded the new docker-compose.yaml and .env files
• copied the correct database information in the new .env
• copied the secrets persistence for gsm at two places in the new docker-compose.yaml in the server and worker service

[Ishankoradia]

• Took backup of airbyte2
• Taking backup of temporal, taking forever. Not sure if its my internet.

[Ishankoradia]

• Took backup of temporal_visibility. This was very small, finished in seconds.
• Table history_node is huge has around 3,10,000 rows in temporal db. Backup just finished

[Ishankoradia]

These set of variables in .env are new

STORAGE_TYPE=local
STORAGE_BUCKET_ACTIVITY_PAYLOAD=payload-storage
STORAGE_BUCKET_LOG=airbyte-dev-logs
STORAGE_BUCKET_STATE=state-storage
STORAGE_BUCKET_WORKLOAD_OUTPUT=state-storage

Kapa says its for logs, but i think we need our logs to be stored in docker volume. Going to check the airbyte on upgrade machine to see where are the logs stored

[Ishankoradia]

Looks like its in the docker volume only even in the airbyte58 ugprade machine.

started airbyte. looks alright. will start Dalgo now

Important: This command can only be run by one of the repository admins:
Usage: ./tools/bin/get_repo_admins.sh <personal_access_token>

[Ishankoradia]

updated the permission of tmp/workspace in airbyte-server, airbyte-worker, airbyte-cron

docker exec -u root -it airbyte-worker /bin/bash
chown -R airbyte:airbyte /tmp/workspace/

Important: This command can only be run by one of the repository admins:
Usage: ./tools/bin/get_repo_admins.sh <personal_access_token>

[Ishankoradia]

Tried a sync on prod and a dbt transform. Both worked.

Important: This command can only be run by one of the repository admins:
Usage: ./tools/bin/get_repo_admins.sh <personal_access_token>