Halaman ini diterjemahkan oleh mesin. Baca versi asli dalam bahasa Inggris.

Feature

core/backup

Has the datastore it is attached to backed up on a schedule, each backup kept for a number of days and then deleted. Every input is the operator's, who attaches it in the Release, under the component's features; the developer writes nothing for it. It applies to components of type stateful-server. On a managed database service, attaching it configures the service's own automated backup: when it starts and how many days each backup is kept. On AWS, the Manifest can also select AWS Backup, which backs up an Amazon RDS instance into a vault of its own under the IAM role infra.role_arn names, the instance keeping its own automated backups beside unless infra.keep_automated_backups is false. On Kubernetes, a backup product the Manifest selects writes to the bucket the store connection points at or, where it can, to a volume infra.volume sizes; an attachment naming both, or neither for such a product, halts. A backup on a volume sits in the same cluster as the data it protects, so it guards against a bad change or deletion but not against losing the cluster. A target refuses by name a value its product cannot keep, rather than running a backup other than the one written: a schedule it cannot express, a retention outside the days it keeps, a key, a role, a user, a store or a volume it has no use for. infra.point_in_time_recovery asks for restores to any moment of the retention window, with no single default: left out, each product keeps its own. It is on, refusing false, on Amazon RDS, Azure Database for PostgreSQL flexible server and CloudNativePG; on in Cloud SQL; off on AWS Backup until true; off, refusing true, on mariadb-operator, Velero, K8up, KubeStash and Kasten.

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:11ad7436b61248c103a4da7832e384846be9510dd4898766b1694fb203214ee9
Dipublikasikan
2026-11-10T10:16:57Z
Identitas penandatangan
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Tanda tangan

  • Resmiapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:7471fef9d0bca516c174bb8096ffab8ebe5f8054f278bb6c300e9352d4fc62f6

Referensi pada versi ini

oci://hub.aggrega.ai/feature/core/backup:1.0.0
Berlaku untuk
component.aggrega.ai/type=stateful-server
Berkonflik dengan
—

Parameter pengembang

Nilai yang ditetapkan pengembang saat melampirkan fitur ini.

Memperluas BaseComponents#/schemas/BaseFeatureParameter

Kontrak keluaran

Nilai yang dipublikasikan fitur ini kepada konsumen.

Tidak ada nilai keluaran yang dideklarasikan.

Anotasi

Tidak ada anotasi yang dideklarasikan.

Relasi

Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.

Menggunakan

Digunakan oleh

Referensi konsep Feature →

Katalog Aggrega — indeks terbuka berisi komponen, fitur, resep, dan plugin yang merendernya.

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi