GitHub Actions: Website deployment previews now dysfunctional

[Lee Calcote]

Hi Ian, Lenox, Bhumika, Ragul, Saurabh, Rajesh, Raunak et al.,

With GitHub Action’s new security policies in place (a good thing), the deployment previews build on each pull request with changes to one of our websites, docs sites, and academies have taken a hit and no longer function - or at this those using this type of workflow don’t function - https://github.com/meshery/meshery/actions/runs/29850097839/job/88700483283.

Last week in the weekly Meshery development meeting, maintainer Ian Whitney walked us through an approach to restructuring our workflows, knowing that this security change is just around the corner. I'm opening up this thread as a follow up, seeking clarity on our chosen path forward. While Ian will ultimately select and sanctify a path forward, he has made an open call for engagement from others in the community to propose, proof, and partner with defining how we refactor.

The answer here might be as simple as one-liner or might involve breakout into multiple workflows, and potentially multiple repos. I'm hopeful for the former or as Matthieu would say, "KISS". Any which way, it behooves us to be extremely consistent whether that is through a custom GitHub Action or simply copy/paste.

Could I ask that this be a topic include in tomorrow's meeting agenda?

Regards,

Lee

[Lennox Wiltshire]

Noted. I presented my proposal for the new workflow in yesterday's meeting so I'll go ahead and present it tomorrow as well. I followed through with Ian's most recent comments so I'll go ahead and message him again over in Slack as well (just in case) so we can find a time to further the enhancement of the workflow.