httk.workflow.projects¶
Compatibility shim over the project anchor, now owned by httk.core.project.
The project anchor — the .httk-project directory, project.json and its
validation, upward discovery, the identity key, and key pinning and trust —
moved to httk-core as httk.core.project so a core-only installation has
projects. This module re-exports that API unchanged (this is an internal move,
so no deprecation is warranted and every public name keeps working) and keeps
the pieces that are workflow policy rather than anchor:
DEFAULT_MANIFEST_EXCLUSIONSandproject_exclusions()— what a signed manifest never records, which is a property of the manifest format and therefore stays here besidehttk.workflow.manifests.initialize_project()andimport_v1_project()— the anchor plus the detached-transfer workspace a workflow project also needs. Creating a workspace atinittime is revisited in Phase 10; for now the behavior is exactly what it was before the anchor moved.
Attributes¶
Functions¶
|
Initialize the project anchor and its detached-transfer workspace. |
|
Create v2 project metadata from a legacy |
|
Module Contents¶
- httk.workflow.projects.DEFAULT_MANIFEST_EXCLUSIONS = ('.httk-project/project.json', '.httk-project/keys/*.seed', '.httk-project/keys/*.priv',...[source]¶
- httk.workflow.projects.initialize_project(root: str | os.PathLike[str], *, name: str, description: str = '', default_queue: str | None = None, manifest_exclusions: collections.abc.Iterable[str] = ()) dict[str, object][source]¶
Initialize the project anchor and its detached-transfer workspace.
The anchor is created by
httk.core.project.initialize_project(); a workflow project additionally gets adetached-transfer-v1workspace. Creating the workspace at init time is the behavior Phase 10 revisits — the anchor and the workspace need not be born together — but it is preserved unchanged here.
- httk.workflow.projects.import_v1_project(root: str | os.PathLike[str], *, source: str | os.PathLike[str] | None = None, name: str | None = None) dict[str, object][source]¶
Create v2 project metadata from a legacy
ht.projectdirectory.The anchor and its adopted legacy identities come from
httk.core.project.import_v1_project(); this adds the workflow workspace on top, exactly as it did before the anchor moved.