Change Instance

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "unit": "https://translate.fedoraproject.org/api/units/13355200/?format=api",
    "component": "https://translate.fedoraproject.org/api/components/fedora-docs-l10n-containers/masterpagesterminologyuse_cases/?format=api",
    "translation": "https://translate.fedoraproject.org/api/translations/fedora-docs-l10n-containers/masterpagesterminologyuse_cases/fi/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2023-03-16T15:34:35.726436Z",
    "action": 59,
    "target": "",
    "old": "",
    "details": {
        "state": 0,
        "source": "When building container infrastructure on dedicated container hosts such as Atomic Host, system administrators still need to perform administrative tasks.  Whether used with distributed systems, such as Kubernetes or OpenShift or standalone container hosts, Super Privileged Containers (SPCs) are a powerful tool.  SPCs can even do things like load specialized kernel modules, such as with systemtap.  In an infrastructure that is built to run containers, administrators will most likely need SPCs to do things like management, monitoring, backups, etc.  It's important to realize that there is typically a tighter coupling between SPCs and the host kernel, so administrators need to choose a rock solid container host and standardize on it, especially in a large clustered/distributed environment where things are more difficult to troubleshoot.  They then need to select a user space in the SPC that is compatible with the host kernel.",
        "old_state": -1
    },
    "id": 10230068,
    "action_name": "String updated in the repository",
    "url": "https://translate.fedoraproject.org/api/changes/10230068/?format=api"
}