- Significant refactor of how resolving works for run/deploy (secrets still needs to be changed). "state_root" no longer exists. An address always contains a target path, which is the state path. This state path is also what will be used to resolve the config. State resolution is no longer first merged and then resolved, but resolved only at the state path location. Argument resolution happens from the resolve root to the state path. The biggest change here is that relative paths in
tidploy.tomlare now resolved relative to themselves and not relative to the (unknown) resolve root, as this is a more natural API. This is also more similar to how things worked pre-0.14. However, execution path still defaults to the resolve root, but this can be modified by addingexecution_path = ".". - Local git cloning now works as it should
- Address system is now used to replace StateIn/StatePaths, deploy now also works similar to before
- A lot of the arguments for the CLI have been changed, so incompatible with 0.14. From now on follows the route to stabilization, as we are basically feature-complete
- Very large update that includes a complete rewrite, currently gated behind
tidploy next. v1 should hopefully make this the default. - There is no backwards compatibility with the portion behind
next, nearly all options have been changed. State resolution is quite different now, with actual loops that try to converge - There is an "address" system that replaces the way download previously worked
- No more archives, this didn't really add anything
- Git tags are handled quite differently now, we use ls-remote to find the correct commit, they are also cached and stored differently
- Added testing and examples
- Start using (color-)eyre which should print the errors in a nicer format and makes especially the more application-level IO errors a lot easier to handle. This also includes a spantrace and a location, which makes it much easier to track where the error actually occurred.
- Small change for match in get secret in secret_store, hopefully fixes strange bug
- Update keyring-rs, more explicitly state platform support. Linux has full support, macOS and Windows are untested but could work.
- Use cache dir to save downloads, use tmp only for the extract target location
- Fix config path traversal
- More consistent deploy path/root path usage
- Git local should work now as a context (not yet fully tested)
- Upload changelog
Significant improvements have been made. Debug logs are available when running with RUST_LOG=DEBUG set as an environment variable.
- Support for cloning from local repositories (almost any Git URL should work now). This also separates some more logic.
runnow works with a deploy path when running an archive.networkoption has been removed, the context now determines this (although it's not yet implemented).
- Fix exe name being overwritten by default value from CLI. Fix run state precedence.
- Upload changelog.
- Deploy and run function added back in. Not compatible with previous versions.
- Most features have been temporarily removed during the refactor. Use v0.9.0 if they are needed. This release contains:
- A major refactor of how state is loaded, to streamline it across commands
- A revamped "auth" command, which now uses a key and by default scopes only to the repo
- A revamped "run" command, which now utilizes the general set state
- dployer is the default option now, dployer_env renamed to env_var and new "run" subcommand
- Add support for dployer, which allows secret loading to also be handled externally by using named pipe communication with Docker containers
- Set default repo to default_git_root_origin and check for git_root_origin in order to read URL from current repo
- Rewrite Git history to fix commit author
- Remove debug URL print
- Separated primitive errors into file
- Fixed extract not having correct path
- Fixed setting password not getting correct name from repo URL