Skip to content

Conversation

@shrutiag161
Copy link
Contributor

  1. In push_to_airflow.sh: I switched gsutil to gcloud storage because gcloud storage is configured to use the temporary access token returned by GCP. gsutil doesn't accept these tokens (so using a temp auth token wouldn't work and we would need to pass in the actual json key file) and is deprecated by Google Cloud.

  2. In an effort to keep permissions separate, I used the github-actions service account which is tied to the github Workload Identity Pool. This service account has "Storage Object Admin" permissions in the necessary GCS buckets accessed by push_to_airflow.sh.

@github-actions
Copy link

github-actions bot commented Oct 28, 2025

No need for rebasing 👍
behind_count is 0
ahead_count is 7

Copy link
Member

@rggelles rggelles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Did you switch service accounts because you wanted to give the new one specific permissions for this?

@shrutiag161
Copy link
Contributor Author

LGTM! Did you switch service accounts because you wanted to give the new one specific permissions for this?

Yeah, the highest level the service account for gsutil/google cloud storage commands needs is Storage Object Admin so I didn't want to use a service account with Storage Admin permissions if I didn't have to. Also just to keep the use cases separate

@shrutiag161 shrutiag161 changed the title Airflow workflow for real Airflow workflow to run push_to_airflow.sh Oct 29, 2025
@shrutiag161 shrutiag161 merged commit 334599b into main Oct 29, 2025
3 checks passed
@shrutiag161 shrutiag161 deleted the airflow-workflow-for-real branch October 29, 2025 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants