initial commit

[20k-ultra]

This is pretty complete and I expect to actually work. I just don't have local instance setup to confirm but it's pretty trivial what's going on..

The developing section needs 1 more piece to actually pass a folder containing a function.

good to merge if someone can confirm via running the test.sh with valid api tokens since I don't have local Lagon instance setup yet.

[20k-ultra]

I'll make this PR not a draft once I get development script to pass a folder to the workflow running so you can actually test locally with a function. done

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9ec5710

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[20k-ultra]

this test runner was removed

PR now contains ways to specify the command, function source, and site_url if you need to test the action with your self hosted instance of Lagon

./test.sh -r lagonapp/github-action@my-dev-branch \
  -f ~/Projects/lagon-function \
  -c "ls" \
  -s "https://lagon.mysite.io"

at a minimum you just need to pass a function

./test.sh -f ~/Projects/lagon-function

[QuiiBz]

Thanks a lot for your help on this!

[20k-ultra]

Ok, action should be merge-able now. Lots of real testing. I have added support for passing in a config object which will override the functions existing one or useful if you never committed one.

Also, another important part I almost forgot. This action allows you to run any CLI command right ? Well that is so you can than perform other steps like maybe send an email of a preview link to your function in a slack channel or something. I have achieved this by saving the CLI output to a local file called lagon.output.

here is an example of the action being used in a workflow to deploy a function than log the preview. You can see the workflow for this here.

here is an example of what the action does if the CLI errors. I encountered lagonapp/lagon#696 which made the action really difficult to exit correctly but I found a decent enough workaround but it's very brittle....

[20k-ultra]

lagonapp/lagon#697 was just posted. I'll get the action working with that once it's merged.

[20k-ultra]

good to go @QuiiBz! I've done a good amount of manual testing (actually running the action and making sure it errors when I wanted it to). I'm confident we can merge this and add more features as people want but the way it's built, it will be flexible enough to do anything you can normally do with local cli installation.

Photo of the action using the example from the readme but I have another step that reads the lagon.output file which the action creates for other steps to process.

[QuiiBz]

Thank you so much for this work!