Page Comparison

...

Axim engineers, as you encounter things about the sandboxes that you wish could be improved, add them here. For items that seem like bugs, also ping in #grove-pr-watcher.

• Access More access

  • to application logs

  Status of sandbox build

  • At a minimum: Always-fail-(Need to have)

  • to the box itself via ssh (Nice to have)

• Better status communication

  • Always fail loudly. That is, “nothing” should never happen, there should always be a comment when the build fails for any reason: when you request a sandbox, something should happen. Either you should get a sandbox, or get a failure notification. No ghosting! 👻 This is true about 80% of the time now, but that 20% is enough to shake our confidence in the system as a whole.

    • Note: We used to have comments for this, but turned them off because they were too noisy. Would there be a less noisy way

    ot

    • of notifying?

    • Idea: Use the GitHub checks system rather than bot comments

    • Idea: Configurable notification levels

    • Idea:

    One comment updated with

    • Use one comment, and amend it to the update the status over time

  • Dashboard of existing sandboxes.

    • Note: you can kinda get at this by filtering on the create-sandbox label

• More examples in the docs on how to do complex configuration, including

  • MFE config

  • Waffle flags

  • Custom MFEs

  • Branches Using branches/tags of Tutor plugins

  • Site configuration (broken link in tutor-contrib-grove)

• ____________________________

• SSH access to the sandboxes

• Deploying from a tag or branch

• ____________________________

• Automatically import the demo course, with configuration it to be from a branch

• More controls

  • Ability to fully destroy and recreate the sandbox without using the remove-label-wait-and-put-it-back workaround described above.

  • Ability to force a redeploy without pushing a commit. This can be desirable when a change is pushed to a dependency other than the PR itself (e.g. a Tutor branch).

  Dashboard of existing sandboxes.

  • Note: you can kinda get at this by filtering on the create-sandbox label

• Auto-provisioned data

  • openedx-demo-course, with configuration fork/branch

  • openedx-test-course, with configuration fork/branch

• Auto-deploy from a tag or branch without having to have a PR

  • master

  • release branches

  • (This was an old action item. It seems unnecessary now that we have Adolfo’s openedx.io sandboxes, unless he wants to stop having to manually manage those)