Feature
core/random-password
A credential the target generates when it deploys, so no one authors it and no default ships for every reader of a catalog to know. The build cannot make the password: its output is identical for identical input and never carries a secret's value. So the FeatureRecipe renders a request instead — a generator resource naming the secret resource it fills — and the target draws the value at deploy time: a controller in a Kubernetes cluster, the random provider during a Terraform apply, Secrets Manager when a CloudFormation stack is created. The rendered output names the generator and the secret resource, and carries no value. It publishes the same locator core/referenced-secret publishes, the secret resource's name and the data key within it, so a consuming component references a generated credential exactly as it references one that already exists, and a slot selecting the credential family admits it. Where several components share one credential, attach core/random-password on one of them and core/referenced-secret, bound to k8s-existing-secret, on the others, with its origin set to the name this attachment publishes; pin that name with the name value so both attachments can be written from one parameter. Attaching core/random-password on each of them, or once at a scope that reaches them all, instead renders one request per component, and each request draws a different password. Realized on helm (through the External Secrets Operator, or through the kubernetes-secret-generator controller), on terraform and on cloudformation. The compose target has no generator, so a Release binding this Feature there halts for want of a realization; supply the credential with core/secret-value instead.
来源
- 内容摘要
- sha256:ed8a7528bc29b9397327cd33ca3cdac57d665c00dc4db06bba85a06eb0fd29b9
- 发布时间
- 2026-11-10T10:17:21Z
- 签名身份
- 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:234dcd7f285e54a007e6995280210313ea3a00da3840df02804519ef9a8d4655
此版本的引用
oci://hub.aggrega.ai/feature/core/random-password:1.0.0- 适用于
- —
- 与之冲突
- —
开发者参数
开发者在附加此功能时设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| key | string | value | 是 | The data key within the generated secret resource under which the password is written, and which a consumer reads. |
| name | string | — | 否 | The name of the secret resource the generator fills, honoured exactly as written. Supplied where another attachment must reference the same credential — core/referenced-secret bound to k8s-existing-secret, with its origin set to this name — so one parameter can feed both. Left unset, the name is derived from the component carrying the attachment and the attachment's own name, as the other credential realizations derive theirs. On helm it names the Secret and must be a valid Kubernetes object name; on terraform it names the random_password resource, with a dot folded to an underscore; on cloudformation it is the Secrets Manager secret's name, and its words, capitalised, form the resource's logical ID. |
| length | integer (min 8, max 128) | 32 | 否 | Length of the generated password, in characters. |
| symbols | boolean | false | 否 | Whether the generated password may contain punctuation. Off by default, because a password is often placed inside a connection string or URL, where a character such as @, / or : changes what the string means. Turned on, each realization uses its generator's own default punctuation set. |
输出契约
此功能向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| name | string | — | 否 | The generated secret resource's locator: the Kubernetes Secret name on helm, the attachment's own module call on terraform, a reference resolving to the Secrets Manager secret's ARN on cloudformation. |
| key | string | — | 否 | The data key within the resource a consumer reads: the Kubernetes Secret data key on helm, the module output carrying the password on terraform, the JSON key within the secret string on cloudformation. |
注解
未声明注解。
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
此实体未使用目录中的任何内容。
被使用
实现
实现
实现
实现