As a developer I would like a template to bootstrap an airflow deployment for prototyping.

• groups
• template trickery

As a user I would like to know that the init command succeeded in a noticable way, regardless of what happens (or doesn't happen) in the init.py script.

I would like to be able to provide a sub command structure so that someone can group commands into logical groups.

i.e.

angreal dev start
angreal dev stop
angreal dev clean

vs.

angreal dev-start
angreal dev-stop
angreal dev-clean

@angreal.group(name="test_",about="commands for testing")
@angreal.command(name="echo", about="")
@angreal.argument(name="phrase", help="the phrase to echo", required=True)
def build_hugo(phrase):
    print(phrase)

invoked with

angreal test_ docs weee

should output

wee

does output

functools.partial(<function group at 0x102e6b060>, name='test', about='commands for testing the application and library')

init behavior doesn't appear to be 100% correct, not checking /angreal prefix for projects in the .angrealrc folder.

As a developer i would like to have a template to bootstrap an airflow provider.

Features:

• code testing
• integration testing
• example dag deployment

https://crates.io/crates/docker-api

Concrete examples here.

https://github.com/vv9k/docker-api-rs/tree/master/examples

As a developer I would like to be able to render a templated folder/file structure from the python api so that i can add structured folders to my project during development.

We should be able to support a context handed or a repl style interface for getting variable values (i.e. angreal.toml, or command generated values)

Example:

• in a python mono repo i would define a python service template and task so that when i execute angreal new service , a new templated structure would appear in the appropriate folder.

angreal.render_templated_director("/path/to/top_dir" , "/path/to/dest/", context = {variable_name: value})


def render_templated_directory(source_path, destination_path, context, remove_on_failure=True):

    try:
         render 
    except:
        if remove_on_failure:
             os.unlink(destination)
       raise

1. refactor init::render_template, pull out the context generator as a seperate function f(path)->context
2. create a context->toml serde function f(context)->map
3. create a render_dir() rust function f(dir,context)->ok()
4. re-implement render-template
5. expose/wrap render_dir() via pyo3, incoming context will need to get serde to context object

Code smells :

• Got a fair amount of copy / pasta and the init::init function doesn't feel very good as a result of hacking.
• Functions aren't returning Result<>, we should use that with unwrap()
• Some internal methods probably aren't namespaced intelligently.

Hi Dylan, we found and issue with angreal, where the method get_os_args is used from click, which has been deprecated. We've created a PR to remove this method from being imported. Thank you

• Document the development process more fully. (how to test, how to release, etc.)
• Update/Expand the tasks for angreal development more fully.
• Add how to / discussion articles on :
• command groups discussion on how chains are build / nested commands can overlap in weird ways if you're not careful
• virtual environments, how they're built / executed on
• docker-py / integration

https://astral.sh/blog/uv

work it into the projects ops cycles and tool integrations where appropriate to continue to chip away at python dependencies.

As a user I'd like to be able to use angreal init <template name> instead of knowing a full repo path.

Options :

• assume the repo is in github to begin with so angreal init test would be angreal init github.com/test.git , angreal init my/test would be angreal init github.com/my/test.git

• create some "official" repos so angreal init test would be angreal init github.com/angreal/test.git

• some mix of the 2

https://docs.python.org/3.7/library/venv.html#venv.EnvBuilder

Create, update, delete, decorator

Pip interface needs to be system calls.

Pretty sure this is because we're doing the work during the initialization of the decorator instead of on call.

Got a report from Rodrigo that initialization is failing with an OS level error on windows. Add testing on all platforms to the CI/CD stack. (angreal run-tests on mac/linux/windows should be sufficient for now)

As an author
I would like to be able to easily render templates, without additional dependencies, within a task
So that I can provide a template task to my users.

Does verbosity even work ?

As a developer I would like an angreal template for bootsrapping angreal templates.

It should include :

• github action for testing template rendering

Users should get a friendly notice of new releases if one exists.

import requests
response = requests.get(f'https://pypi.org/pypi/angreal/json')
latest_version = response.json()['info']['version']

When using a command within an angreal template, the init sub command shouldn't be displayed or available for execution.

Is most certainly broken.

https://github.com/Byron/gitoxide/tree/main/git-repository

Start with :

Clone
Pull

Commit
Push
https://siciarz.net/24-days-rust-git2/

Branch
https://stackoverflow.com/a/67240436/2350761

Tag

Ssh support would be nice.

As a developer,

I would like place a template into {$HOME}/.angrealrc/my-template

So that I can run angreal init my-template

https://docs.python.org/3.7/library/venv.html#venv.EnvBuilder

https://docs.python.org/3.7/library/venv.html#venv.EnvBuilder

Create, activate, decorator.

Pip for installs via system calls.

Rust backed functionality for the python interface :

• docker
• git
• python virtual environments

https://crates.io/crates/docker-api

Common examples here.

https://github.com/vv9k/docker-api-rs/tree/master/examples