fix(week10): PG_DBNAME default/example must be team1, not postgres#8
Merged
Conversation
The shared Azure Postgres database is named team1 (raw data lives in the nyc_taxi schema inside it), not postgres. Students following the previous default/README hit 'permission denied for database postgres' on dbt run even though dbt debug passed (debug only checks that the connection opens, not that the role has grants on that database). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Situatie
A student on the c55 cohort hit
dbt runfailing withpermission denied for database postgreswhiledbt debugreportedAll checks passed!.Probleem
profiles.yml.exampledefaultsPG_DBNAMEtopostgres, and the README/.env.example(merged in #7) told students to keepPG_DBNAME=postgres. The shared Azure Postgres database is actually namedteam1(raw data lives in thenyc_taxischema inside it).dbt debugonly verifies the connection opens; it does not check that the role has grants on the target database, so the wrong default passes debug and only fails on the first real query.Oplossing
profiles.yml.example: defaultPG_DBNAMEtoteam1..env.example:export PG_DBNAME=team1.PG_DBNAME stays team1.Mirrors HackYourAssignment/c55-data-week-10#3. The CI-only dummy value in
.github/workflows/dbt-parse.yml(PG_DBNAME: postgres) is untouched: that job never opens a real DB connection, so it's unaffected.🤖 Generated with Claude Code