potiuk commented on issue #1731: URL: https://github.com/apache/airflow-site/issues/1731#issuecomment-6758779895
Closing this — it's not worth implementing. The archive is eventually consistent anyway: syncs are manually triggered, and a sync that's slower, or waits for the previous one to finish, still converges to the same state in S3 and GitHub. Moving these two workflows to self-hosted runners would add an Infra request, a RunsOn setup to maintain, and the security considerations of self-hosted runners, for a gain that doesn't matter for an archive. The S3 sync workflows stay on `ubuntu-latest`. apache/airflow-site-archive#49 limits each of them to one run at a time (no cancelling) so concurrent syncs can't interfere with each other. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
