fix(assignment): use existing dev_<name> schema, not dev_<name>_borough#5
Merged
Conversation
…>_borough Least-privilege student roles have no CREATE on the database and only own their pre-provisioned dev_<name> schema. Telling students to build into dev_<name>_borough makes their first `dbt build` fail with "permission denied to create schema". Point the assignment at the schema they already own and used all through the Week 10 chapters. - profiles.yml.example: schema dev_<your_name>_borough -> dev_<your_name> - README.md, reports/answers.md: same rename (mart name fct_daily_borough_stats unchanged) - CI dbt-parse.yml: sed placeholder dev_<your_name> -> dev_ci (parse-only, no DB) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The mart's data runs 2023-12-31..2024-01-31, so "across all of January 2024"
was inaccurate. Match the reworded curriculum question ("the whole loaded
dataset"). Pairs with hyf-datatrack assignment data-fact fixes.
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
Week 10 assignment tells students to build into schema
dev_<your_name>_borough(profiles.yml.example, README,reports/answers.md).Probleem
The shared-DB student roles are least-privilege: they have no CREATE on the database and only own their pre-provisioned
dev_<name>schema. A student following the instructions verbatim hitspermission denied to create schema dev_<name>_boroughon their very firstdbt build. A per-deliverable_boroughschema also doesn't generalise: every future assignment would need its own admin-provisioned schema.Oplossing
Point the assignment at the schema students already own and used throughout the Week 10 chapters:
dev_<your_name>.profiles.yml.example:dev_<your_name>_borough→dev_<your_name>README.md,reports/answers.md: same rename (the mart namefct_daily_borough_statsis unchanged).github/workflows/dbt-parse.yml: sed placeholderdev_<your_name>→dev_ci(parse-only job, no DB connection, so purely cosmetic)Verified locally:
dbt buildas a least-priv role intodev_<name>→PASS=12 WARN=1 ERROR=0, 184-row mart. No schema-creation needed.🤖 Generated with Claude Code