Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upload metadata.yaml to GCS bucket on merge to master #24850

Closed
bnchrch opened this issue Apr 4, 2023 · 0 comments · Fixed by #25044
Closed

Upload metadata.yaml to GCS bucket on merge to master #24850

bnchrch opened this issue Apr 4, 2023 · 0 comments · Fixed by #25044
Assignees
@alafanechere
Labels
from/connector-ops

Comments

@bnchrch
Copy link
Contributor

bnchrch commented Apr 4, 2023 •
edited
Loading

What this is

On merge to master

  1. Identify any new metadata files
  2. Check if the file already exist in GCS (/connector/v1.0.0/metadata.yaml and /connector/latest/metadata.yaml)
  3. If not upload them to their respective GCS paths (latest/version).

The reason not to re-upload an existing file is to not mess with updated-at timestamps

Things to note

  1. We want this to be done in a similar fashion to how the validate click command works
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alafanechere alafanechere

Labels
from/connector-ops
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

airbyte-ci: orchestrate the upload of modified metadata.yaml files to GCS airbytehq/airbyte
2 participants
@bnchrch @alafanechere