Repository navigation
Secrets Manager and default bucket share the same name (<naming_pattern>-default) #104
Description
The Secrets Manager instance and the default bucket get the same name:
src/modules/landing-zone/4-secrets-manager.tf:name = "${var.naming_pattern}-default"src/modules/landing-zone/5-bucket.tf:name = "${var.naming_pattern}-default"- same in
src/modules/management/
There is no error, but we document the environment in ArchiMate. There, and in the portal and in alerts, the two can't be told apart by name. This complements #28: the prefix is configurable, but the resource-type part is missing.
Suggestion: add a type abbreviation (e.g. -sm-default, -obj-default). Renaming an existing bucket forces a replace, so a configurable suffix with the current default might be the safer option.
Ref: commit 2bb7c75 (2026-09-29)
Activity
lweberru commentedon Oct 18, 2026
Will look into that.
lweberru commentedon Oct 21, 2026
Resolved by #128 (also fixes #127). The default management and workload bucket names now include the full owning project UUID and a purpose suffix; Secrets Manager keeps its separate existing name. Consequently, Secrets Manager and the default bucket no longer share the same name for the default naming mode. The implementation uses project-qualified names rather than the suggested resource-type abbreviation.
The operator-provided successful real Apply on 2026-10-21 confirms creation of the management buckets with project-qualified names while retaining existing infrastructure. Workload naming is covered by the merged native contract tests; this run did not create an Application workload project. The fix is deployed through Dev release 39608332090.
Compatibility is deliberate: existing installations can explicitly select
bucket_naming = "legacy"to preserve their bucket names. The old name ambiguity can remain in that opt-in compatibility mode. Switching existing buckets to the new mode requires review of the resulting replacement Plan; this closure does not request automatic renaming or migration of existing buckets. English/German compatibility and recovery documentation shipped with #128.