prefecthq / actions-prefect-deploy Goto Github PK

No more deployment.yaml :)

The action should use the new --no-prompt top-level argument introduced in PrefectHQ/prefect#9897 to disable any interactivity.

sample release workflow - https://github.com/google-github-actions/.github/blob/main/.github/workflows/release.yml

The Prefect deploy CLI allows you to specify a --all parameter which deploys all flows defined in your YAML configuration. The action should support this as well.

Create a GHA job/step that can deploy a prefect deployment using projects

submitted a pull request to fix this issue.
#46

• Relates: https://github.com/PrefectHQ/prefect/blob/main/RELEASE-NOTES.md#support-for-custom-prefectyaml-deployment-configuration-files
• Default to be prefect.yaml

currently, it handles only 1 deployment (?)

many users (including myself) prefer pyproject.toml (with setuptools or poetry) after PEP 621

it seems like itd just be a matter of adding an if here basically

# pseudocode
if requirementsfile.endswith(".txt") -> pip install -r requirements.txt
elif requirementsfile.endswith(".toml") -> pip install .
else error out

to allow passing a different path for the prefect.yaml, this action should support the --prefect-file flag

Hi, I'm running into an issue trying to deploy Prefect flows via Github Actions using actions-prefect-deploy@v3 . When I try to run that command locally, I have no issues with using the --prefect-file flag. Would appreciate any assistance thank you!

i know GHA inputs are string values, so we were limited in what we could do here. but i sure do hate listing all the requirement paths + deployment names in a monorepo. maybe --all will help with this, from #17