-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
simplify registry flow #456
base: main
Are you sure you want to change the base?
Conversation
f9584c7
to
b6fa7dc
Compare
b6fa7dc
to
a6e4031
Compare
ecd9764
to
3463c2f
Compare
"secret-str", | ||
"secret-int", | ||
"secret-dict", | ||
"secret-list", | ||
"secret-float", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: handle this case in Block
where we have something like Secret[str]
name: JSON Schema Validation | ||
entry: uv run src/prefect_collection_registry/view_schema_validation.py | ||
language: system | ||
pass_filenames: false | ||
types: [json] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
run JSON schema validation as a pre-commit hook
171ed88
to
e6d9b0b
Compare
add note push code update entrypoint whoops subprocess needs it too
9fb5ce4
to
c13ff5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this necessary now that schema validation is a pre-commit hook?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think so yes bc there's no guarantee someone installs the pre-commit
|
||
|
||
image: prefecthq/prefect:3.1.11-python3.12 | ||
command: uv run --with git+https://github.com/PrefectHQ/prefect-collection-registry.git@main python -m prefect.engine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you overriding the command here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to install the dependencies for the flow, putting uv sync
in a pull step wasn't working for some reason I'd like to figure out later
response = await client.get( | ||
url=f"https://api.github.com/repos/{repo_owner}/{repo_name}/contents/{path}", | ||
headers={"Accept": "application/vnd.github+json"}, | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like you have a lot of different ways to get files from GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes one of them was a duplicate, thanks for catching that, but the other 2 serve different purposes
effectively closes #323
most of the diff is the
uv.lock
filethis pr:
github3
dependencyrun_deployment
to spin up separate infra for specific collections and instead justuv run
the subflow (that handles a single collection) in a subprocessprefect
core by moving it all into python