Great work, Pavan in leading this effort and anyone else who contributed
for this work: Jarek, Jens and team. This is going to be a massive speed-up
for Elad & me and allow even more contributions since we don't have to wait
for 5 mins to checkout the airflow-site repo.


On Fri, 9 May 2025 at 13:49, Jarek Potiuk <ja...@potiuk.com> wrote:

> Good stuff. Excellent job Pavan!
>
> We have a few small teething issues to fix still and update the docs
> describing the architecture and flows (it's optimized for speed so
> necessarily the flows and architecture is a bit more complex than just "git
> push"). But from what I saw over the last few days - this is a game
> changer, we will be able to iterate and improve our docs with minutes of
> turnaround rather than hours to see the effect. Pavan is also working on a
> complete staging workflow - and once we are done, we will be able to test
> and see complete changes to our docs more easily - for example the RC docs
> might be published with "proper" links via the "apache" URLs -
> automatically during release preparation (we missed that so far).
>
> J.
>
>
> On Fri, May 9, 2025 at 9:58 AM Pavankumar Gopidesu <
> gopidesupa...@gmail.com>
> wrote:
>
> > Hello All,
> >
> > We have successfully migrated our documentation publishing process from
> > github to AWS S3.
> >
> > As many of you know, our previous publishing workflow was slow and made
> it
> > difficult for Airflow site release managers and contributors to make
> > changes efficiently. With this transition, the process has become much
> > simpler.
> >
> >
> > Here is the new process for publishing docs:
> >
> >
> > 1. Release managers can now publish documentation to S3 directly via
> GitHub
> > workflows
> >
> >
> > 2. We have created a new repository, airflow-site-archive[1], which
> stores
> > all the historical documentation data. This repository is synced with S3
> to
> > ensure the docs remains up to date
> >
> >
> > 3. Ad hoc or bulk updates can be made to the airflow-site-archive
> > repository. The associated workflows will handle publishing these changes
> > to S3.
> >
> >
> > Updates to the airflow-site main repository now reflect on the live site
> > within approx 3 minutes, yes you heard it right :)
> >
> >
> >
> > Additionally, as part of this migration process, we have fixed all ASF
> CSP
> > non compliant issues. ASF [2]
> >
> >
> > We will soon be enabling a staging website for airflow-site, This will
> > allow all documentation changes to be reviewed before being published to
> > the Airflow live site.
> >
> >
> > Thanks to Jarek, Ash for helping out and giving ideas on the process.
> >
> >
> > Thanks to ASF infra initial discussions.
> >
> >
> > Thanks to elad for his patience, finding and calling out any issues with
> > the updated airflow-site view part of providers release.
> >
> >
> >
> > [1] https://github.com/apache/airflow-site-archive/
> >
> > [2] https://infra.apache.org/csp.html
> >
> >
> > Pavan
> >
>

Reply via email to