Tool · Workflows & capabilities
Alias Resolver
Name your project paths, imports and startup tasks once, then resolve them from one configuration.
Repository: CinvanaAI/alias-resolver
Recorded synthetic example. Source with a complete offline example.
See the idea in action.
The cache task completes, a deliberate startup failure is reported, and shutdown still closes the synthetic database task.
A supplied YAML file, a real synthetic data file, and three supplied lifecycle functions.
{
"path": "data/input.json",
"input": {
"message": "Synthetic lifecycle example"
},
"import_matches_module": true,
"startup": {
"completed": [
"warm_cache"
],
"started_threads": [],
"failures": [
"fail_startup: synthetic startup failure"
]
},
"shutdown": {
"completed": [
"close_database"
],
"started_threads": [],
"failures": []
},
"events": [
"cache warmed",
"startup failed",
"database closed"
]
}Try the example.
From the repository root, follow the dependency requirements in the README. This example uses supplied synthetic material.
python -m pip install -e . python -m examples.walkthrough
The cache task completes, a deliberate startup failure is reported, and shutdown still closes the synthetic database task.
Complete setup and instructions ↗The interesting part.
Path aliases stay within the configuration root; lifecycle calls return structured completions/failures.
Where it came from.
Earlier Apache-licensed YAML path/import/lifecycle alias utility.
Adds an explicit Resolver, containment and configuration checks, CLI, lifecycle results and packaging.
The old FastAPI demonstration is an example, not a runtime requirement.