20c/ctl

Control your environment.

ctl's Issues

Switch to poetry for packaging

Currently blocking on python-poetry/poetry#241

template: should copy access permissions on files it copies

Right now if a templated executable is copied it will be copied without execution permission

Documentation Pass

• proof reading / wording / grammar fixes
• has install instructions
• has quickstart instructions
• has examples
• has generated API documenation
• has changelog section

Version plugin: no longer tag dev versions by default

changelog: version sorting issues in both yaml and md generated output

yaml needs to sort recent (top) to oldest (bottom)

md doesnt numeric sort correctly so 2.10.0 will end up next to 2.1.0 instead of 2.9.0

Better error handling for config errors outside of `plugins`

Example: having a schema error in permissions exits ctl with traceback that's not very telling as to what is failing

reproduce:

permissions:
  namespace: ctl
  permission: crud

semver2 bump patch tries to tag a pre-release

Ran into this today, ran semver2 bump patch without any additional arguments and it tried to tag 1.0.1-rc1, if the --pre-release option isnt specified a pre-release should not be tagged.

flake8 everything

Let's have nice things.

pyhton3.7 support

Code Quality Pass

flake8
add / check / fix lgtm

setup.py url and download_url are wrong

PyPi https://pypi.org/project/ctl/ has bad links because these URLs are incorrect since this project is currently hosted at https://github.com/20c/ctl/ :

ctl/setup.py

Lines 29 to 30 in 312571a

	url='https://github.com/getctl/ctl',
	download_url='https://github.com/getctl/ctl/%s' % version,

Check for known template syntax (jinja2) and error if dependencies are missing

I dont think this needs to be overly complex, probably a simple check for "{%" and "{{" would suffice for now

`version plugin`: work with truncated version in VERSION file

Ran into issue where it couldn't parse the version from the VERSION file as it was missing the patch section.

Reproduce:

Put 0.1 into VERSION file and then try to bump patch

Modernize

• rename master to main
• drop py3.6
• add py3.10
• use 20c github workflow for ci
• update documentation link to gh-pages
• poetry lock

Version and semver2 plugin cause pyproject.toml to lose formatting and comments when writing the new version to it

Figure out why that one mac os test is failing

https://github.com/20c/ctl/runs/2126694491?check_suite_focus=true

Remove python2.7, python3.4, python3.5 official support

venv plugin: copy: remove *.pyc files after copying a venv

venv plugin: copy: remove *.pyc files after copying a venv

Add type hints

Add python3 type hints

One of the git plugin tests is failing

FAILED tests/test_plugin_git.py::test_branch_and_merge[standard] - RuntimeError: error: pathspec 'test' did not match any f...

Add semver 2 support to ctl version plugin

https://semver.org/spec/v2.0.0.html

Add a --pre-release option that allows us to tag pre releases

ctl version bump dev --pre-release beta would do 1.0.0-beta.1
ctl version bump patch --pre-release beta would do 1.0.1-beta
ctl version bump minor --pre-release beta would do 1.1.0-beta
ctl version bump major --pre-release beta would do 2.0.0-beta

Also switch to using https://pypi.org/project/semver/ for the version parsing and updating

venv plugin: add config attribute for rebuild

Add config attribute rebuild that if set will cause build and sync to (re)build the venv even if it already exists.

semver2 plugin confirmation prompt for `bump` action

It'd be nice bump would prompt the user to confirm the new tag via [y/n] before proceeding

git: issue with switching branches

Seems to be some quirkyness when changing the branch on a git plugin

Also should address the fact that github default repo is now called main on new repos

services aren't re-initialized after repo clone

If there is any service init config inside the repo (in the repo_config) they need to be reloaded or at least checked for any differences.

command plugin should display output as it runs

It currently buffers so you can't tell if it's doing anything.

Or at least have an option to allow that, maybe there's situations you wouldn't want that?

venv plugin: allow output override when calling ops directly

Right now operations build, sync and copy will always use the configured value for output

In order for better workflow when operating as part of a plugin chain it would be nice to allow overriding that value directly in the call.

plugin.expose_vars: don't raise on io error

should instead collect such errors and display warnings for them

this is so config template processing doesn't fail before exposed variables are available if it depends on said exposed variables to render in the first place

version plugin: bump needs to do a pull before changelog validation

Otherwise it will try to validate an old changelog file

PyPI plugin: `target` config attribute should be `repository`

This is so it's in line with the version plugin, which currently uses repository to specify the target repository

The pypi plugin currently uses repository to specify which PyPI repository to use, this should change to pypi_repository as well.

Should do this before tagging 1.0.0 since it's a config schema change

move default cachedir

Should be ~/.cache/ctl/

For example, for repos, should be ~/.cache/ctl/repo/github.com/$URL

fix `pypi` and `version` for poetry based projects

• the version inside pyproject.toml is static so version bump should update it
• poetry based projects dont have a setup.py file, pypi release should use poetry build isntead if a poetry.lock file exists

Add python3.8, python3.9 support