StealthOS/subiquity
StealthOS
/
subiquity
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
subiquity/examples/uaclient-status-valid.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

56 lines
1.5 KiB
JSON
Raw Normal View History

Add sample outputs for ua status --simulate-with-token --format json This commit introduces example JSON files that would simulate output of the ua_client script, as in the following command: $ ubuntu-advantage status \ --simulate-with-token "${token}" \ --format json Two files are added, one for each of the following scenario: * output when supplied a valid, non expired token * output when supplied a valid but expired token Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2021-12-09 15:39:00 +00:00
{
"version": "27.4.2~21.10.1",
"effective": null,
"expires": "2035-12-31T00:00:00+00:00",
ubuntu-pro: add subscription info in response to /ubuntu_pro/check_token The response to /ubuntu_pro/check_token now includes information about the subscription: the name of the contract and the "name" of the account. Instead of returning the list of services as an optional field, we now include the list of services in the subscription object. The subscription object is itself marked optional. This is a backward incompatible change. { "status": "VALID_TOKEN", "services": [ { "name": "esm-infra", "description": "UA Infra: Extended Security Maintenance (ESM)", "auto_enabled": true } ] } => { "status": "VALID_TOKEN", "subscription": { "account_name": "user@domain.com", "contract_name": "UA Apps - Essential (Virtual)", "services": [ { "name": "esm-infra", "description": "UA Infra: Extended Security Maintenance (ESM)", "auto_enabled": true } ] } } If the token is not valid, the subscription object will be null: { "status": "EXPIRED_TOKEN", "subscription": null } Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2022-06-30 14:18:44 +00:00
"contract": {
"name": "UA Apps - Essential (Virtual)"
},
"account": {
"name": "user@domain.com"
},
Add sample outputs for ua status --simulate-with-token --format json This commit introduces example JSON files that would simulate output of the ua_client script, as in the following command: $ ubuntu-advantage status \ --simulate-with-token "${token}" \ --format json Two files are added, one for each of the following scenario: * output when supplied a valid, non expired token * output when supplied a valid but expired token Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2021-12-09 15:39:00 +00:00
"services": [
{
"name": "cis",
"description": "Center for Internet Security Audit Tools",
Don't list UA services that are not entitled Instead of only checking if a given UA service is available, we now also check if it is entitled. - the available field for a service refers to its availability on the current machine (e.g. on Focal running on a amd64 CPU) ; whereas - the entitled field tells us if the contract covers the service. Therefore, we need to make sure that we only list the services that are both "available" and "entitled". Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2022-01-25 17:46:48 +00:00
"entitled": "no",
Add sample outputs for ua status --simulate-with-token --format json This commit introduces example JSON files that would simulate output of the ua_client script, as in the following command: $ ubuntu-advantage status \ --simulate-with-token "${token}" \ --format json Two files are added, one for each of the following scenario: * output when supplied a valid, non expired token * output when supplied a valid but expired token Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2021-12-09 15:39:00 +00:00
"auto_enabled": "no",
"available": "yes"
},
{
"name": "esm-apps",
"description": "UA Apps: Extended Security Maintenance (ESM)",
"entitled": "yes",
"auto_enabled": "yes",
Don't list UA services that are not entitled Instead of only checking if a given UA service is available, we now also check if it is entitled. - the available field for a service refers to its availability on the current machine (e.g. on Focal running on a amd64 CPU) ; whereas - the entitled field tells us if the contract covers the service. Therefore, we need to make sure that we only list the services that are both "available" and "entitled". Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2022-01-25 17:46:48 +00:00
"available": "no"
Add sample outputs for ua status --simulate-with-token --format json This commit introduces example JSON files that would simulate output of the ua_client script, as in the following command: $ ubuntu-advantage status \ --simulate-with-token "${token}" \ --format json Two files are added, one for each of the following scenario: * output when supplied a valid, non expired token * output when supplied a valid but expired token Signed-off-by: Olivier Gayot <olivier.gayot@canonical.com>
2021-12-09 15:39:00 +00:00
},
{
"name": "esm-infra",
"description": "UA Infra: Extended Security Maintenance (ESM)",
"entitled": "yes",
"auto_enabled": "yes",
"available": "yes"
},
{
"name": "fips",
"description": "NIST-certified core packages",
"entitled": "yes",
"auto_enabled": "no",
"available": "yes"
},
{
"name": "fips-updates",
"description": "NIST-certified core packages with priority security updates",
"entitled": "yes",
"auto_enabled": "no",
"available": "yes"
},
{
"name": "livepatch",
"description": "Canonical Livepatch service",
"entitled": "yes",
"auto_enabled": "yes",
"available": "yes"
}
]
}