Skip to content

v0.3.2 - Provide custom expressions & Skip logs
Compare
Choose a tag to compare
@puthrayaharness puthrayaharness released this 26 May 17:51
· 70 commits to master since this release
v0.3.2
16cc96b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Important Changes

  1. Improved upgrade logs filtering: The upgrade logs have been enhanced to filter out noisy failures such as duplicate identifiers and duplicate folders by default. This improvement makes it easier to find relevant logs. If you still want to see these filtered logs, you can use the --log-level debug flag with the upgrade command.

  2. Custom expressions for upgrade: Now you can provide custom expressions for an upgrade by passing a YAML file that contains expressions to be replaced with next-gen syntax. This new feature gives you more flexibility in customizing your upgrade process.

  3. Scoped user group creations: You can now scope user group creations to an organization and project, in addition to the default account scope. This enhancement allows for more fine-grained control and organization of user groups.

  4. Changes to overrides with expressions command: The command for providing overrides with expressions has been updated. You should now use harness-upgrade --override FILE expressions syntax to specify the overrides file.

  5. Updated flag for logging level: The --debug flag has been removed. Instead, a new --log-level flag has been introduced, which allows you to set the logging level. The available log levels are trace, debug, info, warn, error, fatal, and panic. Choose the appropriate log level based on your debugging and logging requirements.

Assets 12
Loading