Releases: seal-io/walrus
v0.6.0
Enhancements:
- Introduced the ability to preview changes before upgrading resources, enhancing decision-making and control. Issue #1786
- Expanded our integration capabilities to include Azure and Google Cloud Platform. Issue #1981
- Implemented support for batch adding members to projects, streamlining project setup and management. Issue #950
- Added support for a dark mode in the UI, offering a more comfortable viewing experience in low-light conditions. Issue #1980
- Made several improvements to the CLI user experience, making it more intuitive and efficient. [Issues #1531, #2103, #1741](#1531, #2103, #1741)
Bug Fixes:
- Fixed an issue where clearing search results in breadcrumb navigation caused no other items to be displayed. Issue #2134
- Corrected the behavior where the default value of a variable set to display with
showIf
was not visible when editing a resource. Issue #2132 - Addressed a problem preventing the retrieval of deployment logs in certain failure scenarios. Issue #1660
- Resolved an issue causing Local Walrus to stop functioning after a system reboot. Issue #2140
- Eliminated the continuous logging issue when failing to connect to the terminal. Issue #1649
- Fixed the inconsistent state of child properties after switching items, ensuring reliable user experience. Issue #2112
- Corrected the unexpected results when searching for users by name, improving search accuracy. Issue #2024
For a comprehensive list of changes, please visit the full changelog.
v0.6.0-rc2
fix: add records on run list stream
v0.6.0-rc1
fix: stop pending query error
v0.5.1
Release Notes
Enhancements
- Added support for Walrus CLI on Windows platform. Issue #2069
- Implemented the ability to configure server options for local Walrus instances. Issue #2062
- Added support for exporting a single resource. Issue #2065
Bug Fixes
- Fixed issue where re-applying the same Walrus file could trigger resource patching erroneously. Issue #2055
- Resolved issue where fields were incorrectly marked as required when preset values were present in the matching rule. Issue #2060
- Fixed unexpected confirmation pop-ups triggered after viewing a resource definition and navigating to other pages. Issue #2067
- Addressed issue where Walrus CLI logged out when the current project was deleted. Issue #2063
- Fixed inability to restore hidden array types of variables. Issue #2066
- Resolved issue where leading and trailing spaces in input boxes made parameters ineffective. Issue #2077
- Fixed issue where computed attributes were not being shown. Issue #2088
- Addressed issue where variables with SSH keys could not be used. Issue #2117
For a complete list of changes, refer to the full changelog.
v0.5.1-rc3
fix: support hyphen in workflow variables
v0.5.1-rc2
fix: failed make optional on ancestor node Signed-off-by: thxCode <thxcode0824@gmail.com>
v0.5.0
Highlights
Simplified Resource Management
Services and resources in the previous version are unified in a single comprehensive resource view. Users can now designate an environment as the default. Upon entering the application management page, users will directly navigate to the resource list of the default environment. This consolidated view empowers users to efficiently perform various tasks, such as managing resources, overseeing underlying components, viewing logs, debugging via the terminal, and obtaining service access URLs.
Batteries-Included Environment
Walrus now automatically creates an environment connected to the management Kubernetes cluster by default. It helps to make deployment to kubernetes work out of the box so that users can easily get started. Users can opt out of the default behavior by modifying Walrus configuration on bootstrap.(#1203)
Walrus File
Introducing support for deploying Walrus resources using a YAML format file. Walrus file is similar to docker compose file, but can apply to multi-cloud and hybrid infrastructure. Explore a curated collection of Walrus file examples at Walrus File Hub.
Local Deployment on Docker
Developers can now deploy Walrus files on Docker locally on their PCs. This allows for consistent application specification, matching the one applied to a production Kubernetes environment. No need to run Kubernetes locally—just utilize Docker. (#1710)
Gitee Catalog
Introducing support for the Gitee provider for catalogs, accompanied by a built-in template mirror in Gitee.(#1736)
OpenTofu Deployer
As OpenTofu announces GA, users can now deploy using the stable version of OpenTofu within Walrus.(#1879)
Other Enhancements
Resources
- Added support for redeploy and batch stop/start actions for resources.(#1463)
- Users can now add change comments during upgrade/rollback.(#1445)
Templates
Introduced support for refreshing the template schema of a force-pushed tag.(#1597)
Resource Definitions
- Added built-in resource definitions.(#1708)
- Now supports multiple resource definitions of the same type.(#1784)
- Enhanced support for managing resources provisioned from a definition.(#1754)
Terraform Provider Cache
Implemented cache for Terraform providers to accelerate deployment.(#736)
Walrus CLI
- Improved the readability of outputs.(#1582)
- Added a context switch command.(#1790)
- Now supports specifying the environment for stop/start commands.(#1761)
Bug fixes
For detailed information, refer to: Walrus v0.5.0 Bug Fixes.
v0.5.0-rc4
refactor: ignore resource component useless api
v0.5.0-rc3
fix: use clean tag version for local walrus
v0.5.0-rc2
fix: failed to redeploy resource Signed-off-by: thxCode <thxcode0824@gmail.com>