Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Stage bucket names are inconsistent between DEV and the other stages

Open
  • Is something wrong?
#396 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, python, terraform
Domain
databases, infrastructure

Research direction

Read the bucket definitions in infra/terraform/environments/local/main.tf:86-97 and infra/terraform/environments/aws-poc/main.tf:104-112, then inspect the migration comments and current tests and e2e checks for hard-coded bucket names. Update the naming consistently across stages and address the documented DEV data and catalog migration. Done means both Terraform roots, the bucket list in docs/architecture/local-stack-contracts.md, the upgrade section in docs/setup/local.md, and affected tests and e2e checks use the agreed scheme.

Written by the indexing model from the issue text.

Description

Problem

Medallion bucket names follow two different schemes depending on the stage, and neither matches the stage catalog names (lakehouse_dev, lakehouse_prod).

Stage Bronze bucket today Source
DEV lakehouse-bronze (the v0.2 name, from var.bronze_bucket_name) infra/terraform/environments/local/main.tf:86-97
UAT / PROD ${profile_name}-${stage}-bronze, which is openlakeforge-prod-bronze by default same block

The AWS root does the same (infra/terraform/environments/aws-poc/main.tf:104-112, preserve_legacy_names = name == "dev"). Silver and Gold follow the same pattern.

So a reader can't tell from a bucket name which stage it belongs to: DEV has no stage in its names, and the prefix changes between stages.

Desired naming

One scheme for every stage, aligned with the catalogs:

lakehouse-<stage>-bronze
lakehouse-<stage>-silver
lakehouse-<stage>-gold

So DEV uses lakehouse-dev-* and PROD uses lakehouse-prod-*. The new architecture charts already use these names.

Things to handle

  • Migration. The DEV buckets hold the Iceberg data and metadata that Polaris (local) and Glue (AWS) point to. The comments at local/main.tf:88-91 and aws-poc/main.tf:106-109 keep the legacy names on purpose, so a rename needs either a copy and catalog re-registration, or a documented reset for alpha installs.
  • Prefix. Decide whether the prefix stays fixed (lakehouse) or comes from the Deployment Profile name. If it comes from the profile name, the default profile name and the catalog naming need to agree.
  • Docs. Update the bucket list in docs/architecture/local-stack-contracts.md and the "Upgrading a v0.2 local deployment" section of docs/setup/local.md.
  • Tests and e2e. Update every test and e2e check that hard-codes lakehouse-bronze / -silver / -gold.
Dominant language
Python
Stars
26
Forks
6
Avg merge
12h 14m
Merged PRs (30d)
133

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLakeForge/openlakeforge

All issues in OpenLakeForge/openlakeforge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.