Repository navigation
Run the Cloud course in an instance per participant - #5
Merged
Merged
Conversation
The Cloud course no longer starts from a team card. Each participant gets an instance in the hackathon organization and a service account from the organizers, creates a Kafka cluster, an agent workspace and a SQL workspace in it, and fills in .env with snctl lookups in Lab 0. - Lab 0 reads each address with snctl, creates the login topic and loads it. The seeders accept the cloud stack and name the course in their hints. - Lab 2 selects from the source named after the topic, security.login_events, and offers psql through the SQL workspace gateway. - Lab 4 says the SQL workspace needs read-write MCP access, and its deny example matches what the scripts print. - Troubleshooting covers the snctl context, the SQL tools failing with connection_unavailable, read-only MCP access, and a slow approval. - The doctor and the setup hints point at the instance, not a team card. - What was run: Labs 1, 3 and 4 with every check on all three paths against a test instance on StreamNative Cloud.
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.
Summary
The Cloud course no longer starts from a team card. Each participant works in one shared hackathon organization, in an instance of their own: the organizers hand out a service account and its API key, and the participant creates a Kafka cluster, an agent workspace and a SQL workspace, then fills in
.envwithsnctllookups.snctl, creates the login topic and loads it. The seeders now accept the cloud stack (they refused it before), and a missing topic names the course whose Lab 0 creates it."security.login_events"(the SQL files used"avro.security.login_events"), and offerspsqlthrough the SQL workspace gateway.[error]line the scripts print.snctlcontext, SQL tools failing withconnection_unavailable, read-only MCP access, and an approval the Agent Engine is slow to act on.Verified
Run against a test instance on StreamNative Cloud (
snctl1.8.0,ork0.6.0):psql.Notes for the event
Labs 3 and 4 depend on two settings on each SQL workspace that participants cannot make themselves: a RisingWave version the MCP server can log in to, and read-write MCP access. The troubleshooting page describes both symptoms.
Not run on the Cloud course: the "Try it yourself" tasks and the clean-up at the end of Lab 4.