Releases: arnarg/nixidy
Releases · arnarg/nixidy
v0.4.0
This is a breaking change if your config contains either nixidy.defaults.syncPolicy.automated.*
or applications.*.syncPolicy.automated.*
.
Breaking changes:
- Renamed
applications.*.syncPolicy.automated
toapplications.*.syncPolicy.autoSync
(and the same innixidy.defaults.syncPolicy
) with the addedenabled
option to turn on auto sync. Because of how theApplication
CRD works, the previous setup in nixidy wasn't really able to turn off auto sync.- Essentially by setting both
prune
andselfHeal
tonull
in the CRD will turn off auto sync but the presence of any object undersyncOptions.automated
will turn it on. I decided to make this more intentional in nixidy by requiring to setapplications.*.syncPolicy.autoSync.enabled = true;
.
- Essentially by setting both
Features:
- Added the ability to add annotation to the generated applications in
applications.*.annotations
. - Added abstractions to applications to set compare options under
applications.*.compareOptions
. See available options. - Added abstractions to applications' sync policy to specify select sync options under
applications.*.syncPolicy.syncOptions
. See available options.
v0.3.0
Features:
- Added config option
nixidy.build.revision
which will write the value to.revision
in the root of the built environment directory.- This is intended for chaining environments after one another, i.e. CI definition for building prod watches staging's
.revision
file and builds using the same revision when it changes and opens a pull request.
- This is intended for chaining environments after one another, i.e. CI definition for building prod watches staging's