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.
来源
- 内容摘要
- sha256:11ad7436b61248c103a4da7832e384846be9510dd4898766b1694fb203214ee9
- 发布时间
- 2026-11-10T10:16:57Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/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
此版本的引用
oci://hub.aggrega.ai/feature/core/backup:1.0.0- 适用于
- component.aggrega.ai/type=stateful-server
- 与之冲突
- —
开发者参数
开发者在附加此功能时设置的值。
扩展 BaseComponents#/schemas/BaseFeatureParameter
输出契约
此功能向使用方发布的值。
未声明输出值。
注解
未声明注解。
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 适用于适用于
component.aggrega.ai/type=stateful-server
core/ai-agent/dify-plugin-daemon v1.0.0 →core/ai-tool/filesystem v1.0.0 →core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/weaviate v1.0.0 →core/devtool/harbor v1.0.0 →core/messaging/kafka v1.0.0 →core/messaging/rabbitmq v1.0.0 →core/observability/fluentd v1.0.0 →core/observability/jaeger v1.0.0 →core/observability/loki v1.0.0 →core/observability/prometheus v1.0.0 →core/observability/tempo v1.0.0 →core/security/openbao v1.0.0 → - $ref扩展模式(values)
BaseComponents#/schemas/BaseFeatureParameter
被使用
实现
实现
实现
实现
实现
实现
实现
实现
实现
实现