Repository navigation
Support catalogs - #176
Merged
Merged
Support catalogs#176
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds initial support for a project catalog. Tasks can publish values to the catalog, read current values, and wait for the next value. Waiting works with suspense, so an execution can go to sleep until an update become available.
A catalog can be defined at the module level, it can be typed, and its path an be parameterised:
Within a task, use
.at(...)to resolve the placeholders (if needed), and.publish(...)to write a new value:If Pydantic is installed, types are validated at publish and read.
Within a task use
.current()to get the latest value (relative to an execution's snapshot) - this will block (or suspend) if no value is available:Or use
.next()to suspend execution, deferring to an execution snapshotted against the next version (when available):Catalogs are scoped to a workspace using the same inheritance rules as elsewhere.