Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore/context around deployment files #37

Merged
merged 3 commits into from
Jan 18, 2024
Merged

Chore/context around deployment files #37

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5843ef3
readme snippit
jimid27 Jan 18, 2024
a9bce5a
Add note under the inputs
jimid27 Jan 18, 2024
ecc1532
Verbiage
jimid27 Jan 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,8 @@ Additionally, the `prefect deploy` command needs to load your flow in order to g
| deployment-file-path | Relative path to your Prefect deployment file. Defaults to `./prefect.yaml` | false |
| all-deployments | If set to "true", all deployments defined in prefect.yaml will be deployed. This will override the deployment-names input. Defaults to "false" | true |

**Note**: When setting the `deployment-file-path` only associate deployment-names that are included in that deployment file. If you attempt to pass a prefect deployment that is not included in that file, the action will fail.

## Examples

### Simple Prefect Deploy
Expand Down