fix(week10): require SSL for Azure Postgres + add .env.example#7
Merged
Conversation
- profiles.yml.example: add sslmode: require (Azure Database for PostgreSQL needs an encrypted connection). - add .env.example with PG_* exports so students copy to .env, fill in the password, and source it instead of retyping exports. - README Task 1: switch from ad-hoc exports to the cp .env.example .env + source .env flow. 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
Students connect the Week 10 dbt project to the shared Azure Database for PostgreSQL. The connection template (
profiles.yml.example) had no SSL setting, and there was no.env.example— the README asked students to retype fourexportlines by hand every session.Probleem
sslmode. Azure Postgres expects an encrypted connection. Relying on libpq's implicitpreferdefault is fragile and undocumented; a student on a stricter server or a different client gets a confusing connection error atdbt debug..env.example..gitignorealready whitelists!.env.example, but the file never existed, so the intended copy-and-source workflow wasn't available.Oplossing
profiles.yml.example: addsslmode: require..env.examplewith thePG_*exports; studentscp .env.example .env, fill in the password, andsource .env.exportblock with thecp .env.example .env+source .envflow, and add the new file to the tree diagram.Mirrors HackYourAssignment/c55-data-week-10#2 so the next cohort inherits the same fixes. No model/test/grader logic changes.
🤖 Generated with Claude Code