feat(web): re-introduce the storage encryption settings#2031
Merged
joseivanlopez merged 18 commits intomasterfrom Feb 21, 2025
Merged
feat(web): re-introduce the storage encryption settings#2031joseivanlopez merged 18 commits intomasterfrom
joseivanlopez merged 18 commits intomasterfrom
Conversation
dgdavid
commented
Feb 20, 2025
dgdavid
commented
Feb 20, 2025
| import { ActionGroup, Alert, Checkbox, Content, Form, Stack, Switch } from "@patternfly/react-core"; | ||
| import { Page, PasswordAndConfirmationInput } from "~/components/core"; | ||
| import { EncryptionMethods } from "~/types/storage"; | ||
| import sizingStyles from "@patternfly/react-styles/css/utilities/Sizing/sizing"; |
Contributor
Author
There was a problem hiding this comment.
I'd like to drop this and its usage, but need a bit more of time for testing how to limit the width used by the Checkbox description without affecting to the rest of the form and allowing Form#isWidthLimited to do its work properly.
Will invest some time on Monday, if priorities permits.
17b590a to
19ea4df
Compare
Pull Request Test Coverage Report for Build 13459450863Details
💛 - Coveralls |
e5670df to
298e066
Compare
This comment was marked as resolved.
This comment was marked as resolved.
298e066 to
3d6a47d
Compare
Contributor
I will fixed with a hack just for today. |
This comment was marked as resolved.
This comment was marked as resolved.
3d6a47d to
322710e
Compare
It is not a "field" anymore.
This commit simplifies the encryption section by displaying only useful, read-only information to users and providing a consistent "Edit" action to navigate to the encryption settings page, where users can adjust the settings.
It will no longer be a modal dialog, but a page instead.
Now implemented as a form in its dedicated route/page. Note that: * It's unclear how to handle the isEnabled status—whether to hide the rest of the widgets or disable them. Disabling them allows users to see what they'll find, but we should apply the same approach across all forms, which isn't currently the case for the RootUserForm. * Tests are still pending, as we're not using real hooks, making testing difficult. Recreating fake tests would not be worthwhile.
2ab59aa to
07f61b1
Compare
ancorgs
reviewed
Feb 21, 2025
service/lib/agama/storage/config_conversions/from_model_conversions/encryption.rb
Outdated
Show resolved
Hide resolved
ancorgs
reviewed
Feb 21, 2025
service/lib/agama/storage/config_conversions/to_model_conversions/encryption.rb
Outdated
Show resolved
Hide resolved
ancorgs
reviewed
Feb 21, 2025
dgdavid
commented
Feb 21, 2025
dgdavid
commented
Feb 21, 2025
6ab8dbc to
544c138
Compare
ancorgs
approved these changes
Feb 21, 2025
Contributor
ancorgs
left a comment
There was a problem hiding this comment.
LGTM. This is, of course, far from perfection. But it exactly what we need (and can afford) now.
Merged
imobachgs
added a commit
that referenced
this pull request
Feb 26, 2025
Prepare for releasing Agama 12: * #1858 * #1887 * #1890 * #1892 * #1893 * #1894 * #1896 * #1898 * #1899 * #1900 * #1901 * #1906 * #1908 * #1909 * #1910 * #1911 * #1912 * #1914 * #1915 * #1917 * #1919 * #1920 * #1921 * #1922 * #1923 * #1924 * #1926 * #1927 * #1928 * #1929 * #1930 * #1931 * #1932 * #1933 * #1934 * #1935 * #1936 * #1937 * #1938 * #1939 * #1942 * #1943 * #1945 * #1948 * #1949 * #1952 * #1953 * #1954 * #1955 * #1957 * #1958 * #1959 * #1961 * #1963 * #1964 * #1967 * #1969 * #1970 * #1971 * #1972 * #1973 * #1974 * #1975 * #1976 * #1977 * #1979 * #1980 * #1981 * #1982 * #1984 * #1986 * #1987 * #1988 * #1990 * #1991 * #1992 * #1993 * #1995 * #1996 * #1997 * #1999 * #2000 * #2001 * #2002 * #2003 * #2004 * #2005 * #2006 * #2007 * #2008 * #2009 * #2010 * #2011 * #2012 * #2013 * #2014 * #2015 * #2016 * #2017 * #2019 * #2021 * #2022 * #2025 * #2027 * #2029 * #2030 * #2031 * #2033 * #2034 * #2035 * #2036 * #2037 * #2038 * #2039 * #2040 * #2045 * #2046 * #2050 * #2053 * #2054 * #2055 * #2056 * #2058 * #2060 * #2061 * #2062 * #2063 * #2064 * #2066 * #2067 * #2068 * #2069 * #2070 * #2071 * #2072 * #2073 * #2075 * #2076 * #2080 * #2082 * #2083
bmwiedemann
pushed a commit
to bmwiedemann/openSUSE
that referenced
this pull request
Feb 26, 2025
https://build.opensuse.org/request/show/1248595 by user IGonzalezSosa + dimstar_suse - Version 12 - Add the missing shebang line to the agama-scripts.sh shell script (gh#agama-project/agama#2077). - Save logs after running post installation scripts (gh#agama-project/agama#2078). - Keep the encoding when storing the locale (gh#agama-project/agama#2062). - Extend storage model schema to support global encryption (gh#agama-project/agama#2031). - Introduce the storage model to support the new storage user interface (gh#agama-project/agama#2033) - Expose root and first user passwords (gh#agama-project/agama#2005). - Remove support for auto-login. - Added reboot command to the CLI (gh#agama-project/agama#1970) - Set console and X11 keymaps when changing the installer keymap (bsc#1236174). - Use the "dashed" form of the keymap identifier when calling systemd-firstboo
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First iteraration to bring the encryption section back.
The implementation at backend side is very simplistic and it does not properly work with several scenarios, for example:
In those cases, the model considers that all the new partitions are encrypted, and the encryption config is taken from either the root partition or any other encrypted partition.
Note that these scenarios can only happen if a custom config is loaded. They cannot be accomplished by using the UI.