SL-667: Add CICD config for Javabuilder demo env

[ebeastlake]

Adds a new javabuilder-demo stack for Java Lab eval mode.

Tickets:

• https://codedotorg.atlassian.net/browse/SL-666
• https://codedotorg.atlassian.net/browse/SL-667

Outstanding questions:

• How do we modify javabuilder/template.yml.erb so that it doesn't use (or effectively ignores) the TeacherAssociatedRequests table (here) and the TeacherLimitPerHour (here)? Will address this later per SL-667: Add CICD config for Javabuilder demo env #385 (comment).

[ebeastlake]

@molly-moen I still need to add something here, yeah? https://github.com/code-dot-org/javabuilder/blob/main/cicd/3-app/javabuilder/template.yml.erb#L1118

I specified the javabuilder-demo subdomain in the YML file config, so this template should produce wss://javabuilder-demo.code.org, but where does that value get exposed? (i.e. These templates and URLs are 1-1 with the env files, but I need dashboard to be 1-2 with URLs, and I don't see where I do something like JavabuilderDemoURL = *).

[cat5inthecradle]

I think this is what you're discussing in other comments. For clarity, I'd suggest adding this to the other config files with whatever our default value is.

[cat5inthecradle]

But this would be safe to deploy as-is. You could also remove that config parameter at this time, and add it later as it's own PR.

[cat5inthecradle]

In fact, that's what I'd recommend. Remove the TeacherLimitPerHour part from this PR, then we can merge this and make sure we've got a green pipeline into this new environment before adding new config parameters.

[cat5inthecradle]

LGTM! To deploy this change, after merging, we just need to run the following.

cicd/2-cicd/deploy-cicd.sh

There might be a bit of pain to do with ruby versions or AWS credentials. Once you merge, switch back to main on your local, pull this new code, then run cicd/2-cicd/deploy-cicd.sh. Ping me on slack and I can follow along and help troubleshoot any issues.

[sanchitmalhotra126]

I specified the javabuilder-demo subdomain in the YML file config, so this template should produce wss://javabuilder-demo.code.org, but where does that value get exposed? (i.e. These templates and URLs are 1-1 with the env files, but I need dashboard to be 1-2 with URLs, and I don't see where I do something like JavabuilderDemoURL = *).

Yep, updating Dashboard (and the frontend) would be a separate change -

Dashboard reads the Javabuilder websocket and HTTP endpoints here and here (in cdo.rb). Currently we just default to the prod URL (unless overridden via DCDO, or by local environment config), so we'll have to update some logic to serve the correct URL to the client based on the situation. We read the websocket URL value from the config in our back end here in javalab.rb, which is served to the front end as part of the level info. The actual websocket request, using the given URL, is made here (in JavabuilderConnection). The HTTP url is used in the backend only when making the initial put sources call; that's read here (in javalab_files_helper).

[sanchitmalhotra126]

One question out of curiosity, but otherwise LGTM!

[sanchitmalhotra126]

Probably a question for @cat5inthecradle - is it possible/should it be possible to target a branch other than main for a production deploy?