Changing the default runner after initial setup.

[Raphael-Mabille]

When I first did the set-up for GLA in vs_code it prompted me for the image I wanted to use in the runner.

After that I could run jobs no problem, but I want to change the image used in my runners.

The problem is that in the settings tab, there is no Runners registered or any option to add one.

The workflow I run is a workflow that uses another workflow referenced in github where the runner to use is defined (ubuntu latest).

name: Deploy
on:
  workflow_dispatch:
  push:
    branches: [master]
jobs:
  deploy:
    name: "Deploy project"
    uses: redacted/workflows/.github/workflows/deploy.yml@main
    with:
      environment: Production Kinsta
      url: "https://redacted"
      branch: master
      args_rsync: "--exclude=web/signature"
      target: "public"
      pagespeed: true
      threshold: 80
    secrets:
      SSH_PRIVATE_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
      REMOTE_HOST: ${{ secrets.REMOTE_HOST }}
      REMOTE_USER: ${{ secrets.REMOTE_USER }}
      REMOTE_PORT: ${{ secrets.REMOTE_PORT }}

[SanjulaGanepola]

Hello @Raphael-Mabille. You will need to first set the runs-on field in your workflow for it to be detected in the Settings view. For example:

[Raphael-Mabille]

Thank you for such a quick answer,

I can't really add that line in my workflow as the jobs are defined in another workflow and so the runs-on is also defined in that other workflow.

workflow that is in my vscode workspace:

...
jobs:
  deploy:
    name: "Deploy project"
    uses: redacted/workflows/.github/workflows/deploy.yml@main
    with:
...

remote workflow stored on github (deploy.yml):

name: Deploy project
on:
  workflow_call:
...
jobs:
  deployement:
    name: "Deploy project"
    runs-on: ubuntu-latest
...

When I run the workflow using GLA, it follows the link to the remote workflow and initialize ubuntu-latest correctly. The outcome I am looking for is for it to use the ubuntu-latest=catthehacker/ubuntu:full-latest Image.

Currently it defaults to act-latest.

The first time I initialized the extension it prompted me to download a light, medium or large image. I chose medium at the time and am looking to change it to large. But maybe I misunderstood the setup and the options weren't used to choose which version of the image to use as default ?

Thanks for your time.

[SanjulaGanepola]

Interesting. At the moment, the extension only supports setting the -P, --platform option if the runs-on key is present. In your case, what you can still do is set the default from your global act config. You can see what the default is by running the act --bug-report command:

In your case, you will probably see act-latest since that is the default medium image as documented here. You can change it to use ubuntu-latest=catthehacker/ubuntu:full-latest in this file.

[Raphael-Mabille]

Thank you, I will try that out and come back if I get some good results.

[Raphael-Mabille]

So I did manage to swap the default thanks to your advice, but another problem arose.
I think what cause my workflow to fail now is that my secrets don't carry over to the remote workflow.
I won't investigate further into that issue as I don't really have time to work on that anymore.

anyway thanks for your help and thanks for sharing such an interesting add-on.

[SanjulaGanepola]

@Raphael-Mabille Secrets can be specified in a couple different ways as described here. In your specific case, it looks like you are trying to propagate the secrets to the remote workflow. Are these the same exact secrets or different ones? I personally have not tried this, but I would suggest using the .secrets file mentioned in the docs. If you ever get a chance to try it out and again run into the same issue, please let me know. I would be happy to help.