-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata Upload: target production GCS bucket #25529
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat!
Do you think we should double check that the current branch is master, and use the dev bucket when it's not?
@@ -28,7 +28,7 @@ jobs: | |||
GCP_GSM_CREDENTIALS: ${{ secrets.GCP_GSM_CREDENTIALS }} | |||
GCS_CREDENTIALS: ${{ secrets.METADATA_SERVICE_DEV_GCS_CREDENTIALS }} | |||
METADATA_SERVICE_ACCOUNT_KEY: ${{ secrets.METADATA_SERVICE_DEV_GCS_CREDENTIALS }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bnchrch this SA should be updated too. I think we now have permission to create sercrets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!
18363dd
to
830c721
Compare
* Update spec mask to be generated from sensor * Update publish to use production bucket * Update env variable
What
We need metadata files uploading to the production bucket
closes #25091
How
This updates publish to target prod-airbyte-cloud-connector-metadata-service instead of dev-airbyte-cloud-connector-metadata-service
This also updates our spec mask to generate at the same time as the registry
Before merge
After merge