00 — Getting Started#
Everything in this training happens inside the Dynatrace Enablement app: you write, run, test and ship a training in the app's training editor. You need a Dynatrace tenant with the app, a GitHub account, and a browser — nothing else. No VS Code, no Codespace.
1. Install the app#
Go to Orbital and register your tenant with an account OAuth client — the required scopes are listed on the page:
autonomous-enablements.whydevslovedynatrace.com/#register
The app installs in your tenant as Dynatrace Enablement. Orbital uses the client once to install the app and store it in the tenant for token minting and self-updates; Orbital itself keeps nothing.
No tenant of your own?
Use the SE sandbox tenant — the app is already deployed there.
2. Turn on the Training Creator#
The editor is the Editor entry in the app's header, after Progress. It is switched per tenant, by anyone in it, and it is off by default. Open Editor; on a tenant where it is off the page reads Training Creator is turned off on this tenant. Press Turn on for this tenant.
You can switch it on or off again at any time under Administration → Training Creator, which also shows who changed it last.
No Editor entry in the header?
The Editor entry only appears where the platform offers the training editor. If your tenant shows none — or the page says The training editor is not available on this environment — use a tenant where it is offered, or build the training the classic way described in the appendix.
3. Connect GitHub#
Your training is a GitHub repository, and the editor commits to it as you. In the editor's top right corner press Sign in to GitHub and approve the GitHub window that opens. Once connected, your GitHub handle (@you) sits in the top right corner, next to Disconnect.
To push to a repository, the editor's GitHub App must be installed on the repository's owner. When it is not, the editor says so and offers Install App on <owner> — or a fork to your own account (see 01 — Open or Fork a Training).
4. Take Kubernetes 101 as a learner#
Open Trainings and run Kubernetes 101 from start to finish. This is the most important step: it shows you the learner experience you are about to build — the terminal, the checks, the quizzes, the DQL validations and the progress tracking. (The Show solution / Run solution buttons appear for trainers; learners see them only when a tenant admin turns on Enable solutions.)
5. The flow from here#
Each of the next pages is one thing you do in the editor, in the order you do it:
| Page | In the editor |
|---|---|
| 01 — Open or Fork a Training | the entry selector: a training, its branches, Fork, Create branch, + Import from URL |
| 02 — Start the Environment | Start environment, the Workspace, Open terminal, the Provisioning Log |
| 03 — Command Center | run a command, pick a framework function, run DQL |
| 04 — Write and Test Steps | Source / Preview / Split, Insert, Problems, Test step, Run test, Run validation |
| 05 — Recreate the Environment | Recreate container, Recreate from branch, Restart |
| 06 — Commit and Open a PR | Commit, History, Create PR |
| 07 — Test as a Learner | Preview for learners, then the merged training |
The Reference pages (How It Works, Automate the Environment, Lesson Anatomy, Interactive Blocks, Example Lesson) explain what you write; the flow pages explain where you write and test it.
First check: is your environment up?#
This template is itself an interactive training. The check below runs in your container — it is the same checkNodeReady helper you will find in my_functions.sh: