# Stork 1.9.0 Release Notes, February 1st 2023 Welcome to Stork 1.9.0, another development release. The changes introduced in this version are: 1. **Kea Configuration Management**: Stork now recognizes the formats of standard DHCP options. For each option specified for a host reservation, it automatically opens a form with the appropriate option fields; the user no longer needs to manually add option fields unless the option carries an array of fields. In this case, the first field of the array is automatically added, and the remaining array fields (if any) must be added manually [#912, #937]. DHCPv4 fixed fields are now supported in reservations [#911]. The design is now complete [#599]. The subnet-id information is now displayed on the subnets list page [#376]. 2. **User deletion**: Users can now be deleted by super-admins. It is not possible to delete the last super-admin, as a safety net [#117]. 3. **PD pools**: Stork is now able to handle Prefix Delegation pools [#186]. The address and PD pools are now updated properly [#196, #927]. 4. **Logging levels**: Stork now has configurable logging levels - DEBUG, INFO, WARN and ERROR - that can be specified using the STORK_LOG_LEVEL variable [#870]. 5. **Bugfixes**: It is now possible to delete machines with config reports [#928]. The HA state no longer disappears when switching between tabs [#448]. Communication events are now bound to the machine and will be listed/filtered properly [#882]. Fixed an old migration (13) to handle situations where migrating shared networks could crash the server [#196]. Daemon statuses are no longer duplicated when a machine runs multiple daemons [#900]. Improved icons to filter the config checkers reports [#916]. 6. **Build improvements**: The demo now builds properly [#960]. Shellcheck linter for shell scripts is now part of the CI checks [#876]. Manual pages are now properly included in the native packages [#913]. Storybook, a developer tool, has been downgraded to 6.5.12 [#926]. Fixed one unstable test [#916]. 7. **Security**: Many dependencies have been updated, to address known security vulnerabilities [#934]. The CI now uses CodeQL (a replacement for the LGTM service) to assess code correctness [#946]. The go linter now refuses new go functions without comments. Missing comments for existing functions were added [#906]. Govulncheck, a vulnerability checker, is now used to review used third-party libraries against known vulnerabilities [#861]. Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues. ## Incompatible Changes None. ## Release Model Stork has bi-monthly development releases, with some exceptions. We encourage users to test the development releases and report back their findings on the stork-users mailing list, available at https://lists.isc.org/mailman/listinfo/stork-users. This text references issue numbers. For more details, visit the Stork GitLab page at https://gitlab.isc.org/isc-projects/stork/issues. ## License Stork is released under the Mozilla Public License, version 2.0. https://www.mozilla.org/en-US/MPL/2.0 ## Download The easiest way to install the software is to use native deb or RPM packages. They can be downloaded from: https://cloudsmith.io/~isc/repos/stork/ The Stork source and PGP signature for this release may be downloaded from: https://downloads.isc.org/isc/stork The signature was generated with the ISC code-signing key, which is available at: https://www.isc.org/pgpkey ISC provides documentation in the Stork Administrator Reference Manual (ARM). It is available on ReadTheDocs.io at https://stork.readthedocs.io/en/latest/, and in source form in [the doc/ directory](https://gitlab.isc.org/isc-projects/stork/-/tree/master/doc). We ask users of this software to please let us know how it worked for you and what operating system you tested on. Feel free to share your feedback on the stork-users mailing list (https://lists.isc.org/mailman/listinfo/stork-users). We would also like to hear whether the documentation is adequate and accurate. Please open tickets in the Stork GitLab project for bugs, documentation omissions and errors, and enhancement requests. We want to hear from you even if everything worked. ## Support Free best-effort support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/mailinglists/. If you have any comments or questions about working with Stork, please share them to the stork-users list (https://lists.isc.org/mailman/listinfo/stork-users). Bugs and feature requests may be submitted via GitLab at https://gitlab.isc.org/isc-projects/stork/issues. ## Changes The following summarizes changes and important upgrades since the previous Stork release versioned 1.8.0. * 277 [bug] slawek Fixed a bug that prevented the machines from deleting. (Gitlab #928) * 276 [func] razvan Added functionality for deleting users. A super-admin cannot remove its own account and the last super-admin user cannot be removed. (Gitlab #117) * 275 [bug] slawek Fixed the security vulnerabilities reported by the Github Dependabot and updated some dependencies. Added some Rake tasks for updating the project dependencies. Upgraded the target JavaScript version of the output UI bundle to be ES2020 standard-compliant. (Gitlab #934) * 274 [bug] slawek Fixed detecting changes in the subnets' configuration. Stork now recognizes modifications of the subnet's client class, address pools, and delegated prefix pools. (Gitlab #927) * 273 [func] marcin DHCP option form automatically shows controls suitable for the selected standard option definition. Previously, a user had to know the option format and manually add option field controls. (Gitlab #937) * 272 [func] tomek Stork agent, server and tool now have logging levels configurable using STORK_LOG_LEVEL environment variable. The allowed values are: DEBUG, INFO, WARN, ERROR. (Gitlab #870) * 271 [bug] slawek Added a waiting indicator presented while loading the HA servers' statuses. Previously, an inappropriate message about missing HA configuration was displayed. (Gitlab #448) * 270 [func] slawek Extended the UI to display the delegated prefix pools and their utilizations. (Gitlab #186) * 269 [build] slawek Added missing comments for all exported functions and enabled a linter rule to make them mandatory. (Gitlab #906) * 268 [func] slawek The subnet ID presents a value from the Kea configuration instead of the internal Stork database ID. (Gitlab #376) * 267 [build] slawek Added govulncheck to the Stork build system, a tool to detect security vulnerabilities on the backend. (Gitlab #861) * 266 [bug] slawek The events pertaining to the daemons and apps can be filtered by the machines running these daemons and apps. Previously, filtering by a specific machine or an app did not return some events related to daemons. (Gitlab #882) * 265 [bug] slawek Fixed the database migration that interrupted the schema upgrade if the database contained any shared networks. (Gitlab #196) * 264 [func] marcin Added configuration of the DHCPv4 siaddr, sname, and file fields in the Kea host reservations. (Gitlab #911) * 263 [build] andrei Added the lint:shell rake task which calls shellcheck on all shell scripts. Added a CI step that calls this linter. Improved the shell scripts to appease the shellcheck warnings. (Gitlab #876) * 262 [bug] slawek Removed duplicated statuses of daemons on the machine page when the machine runs multiple applications. (Gitlab #900) * 261 [build] slawek Fixed the missing man pages for Stork programs installed by packages. (Gitlab #913) Thank you again to everyone who assisted us in making this release possible. We look forward to receiving your feedback.