Skip to content

Releases: tiptenbrink/tidploy

v0.16.0

16 May 10:44
35a28e9
Compare
Choose a tag to compare
  • 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.toml are 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 adding execution_path = ".".
  • Local git cloning now works as it should

v0.15.0

07 May 14:17
5c76739
Compare
Choose a tag to compare
  • 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

v0.14.0

05 May 11:06
2d7032d
Compare
Choose a tag to compare
  • 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.

v0.13.1

16 Mar 21:17
6577e74
Compare
Choose a tag to compare
  • Small change for match in get secret in secret_store, hopefully fixes strange bug

v0.13.0

13 Jan 14:35
1c896ce
Compare
Choose a tag to compare
  • 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)

v0.12.1

12 Jan 11:03
94879a5
Compare
Choose a tag to compare
  • Upload changelog

v0.11.2

15 Dec 20:38
7930bdb
Compare
Choose a tag to compare
  • Fix exe name being overwritten by default value from CLI. Fix run state precedence.

v0.11.1

15 Dec 20:23
4051532
Compare
Choose a tag to compare
  • Upload changelog.

v0.10.0

15 Dec 13:21
b922a91
Compare
Choose a tag to compare
  • 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

v0.9.0

14 Dec 13:29
b33d282
Compare
Choose a tag to compare
  • dployer is the default option now, dployer_env renamed to env_var and new "run" subcommand