This document tries to define how self-update should behave in different scenarios. It contains also some information about which changes should be made.
- Minimize the amount of error messages. In a nutshell, we should
| # Copyright (c) [2019] SUSE LLC | |
| # | |
| # All Rights Reserved. | |
| # | |
| # This program is free software; you can redistribute it and/or modify it | |
| # under the terms of version 2 of the GNU General Public License as published | |
| # by the Free Software Foundation. | |
| # | |
| # This program is distributed in the hope that it will be useful, but WITHOUT | |
| # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or |
| <?xml version="1.0"?> | |
| <!DOCTYPE profile> | |
| <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> | |
| <% home_in_sdb = disks.map { |d| d[:device] }.include?("sdb") %> | |
| <partitioning config:type="list"> | |
| <drive> | |
| <device>/dev/sda</device> | |
| <disklabel>gpt</disklabel> | |
| <enable_snapshots t="boolean">true</enable_snapshots> |
This document summarizes the result of the Relm4-based user interface for Agama which was part of SUSE’s Hack Week 23. It was just an experiment and I do not plan to continue working on it.
However, I will keep the branch in my fork in case anyone is interested, but bear in mind that the code quaility is far from production-ready.
The initial idea of the project was to play around with Relm4 and build a simple user interface for Agama. At the end of the, the following features were implemented:
| TOKEN=$(curl --silent http://localhost:3000/api/auth -d '{"password": "your-password"}' \ | |
| -H "Content-Type: application/json" | jq .token | tr -d '"') | |
| echo $TOKEN | |
| echo "Content-Type: application/json" >headers.txt | |
| echo -n "Authorization: Bearer " >>headers.txt | |
| echo $TOKEN >>headers.txt | |
| curl --silent -H @headers.txt \ | |
| http://localhost:3000/api/software/products | jq |
This document includes some small scripts that you can use to interact with Agama's API from the CLI. You must define the Agama's server URL using the AGAMA_URL (e.g., https://192.168.122.10).
The following script logs in and writes the headers to use in the subsequent calls in the headers.txt file. Adjust the password (linux) to your use case.
#!/usr/bin/bash