Workshop Troubleshooting

Secrets Access - VAULT_TOKEN_DOJO

The earliest indication of this is in the wwg-internal/action-code-artifact-nodejs-login or any step that requires ${{ secrets.VALUT_TOKEN_DOJO }}. To validate this is the issue, the participant can navigate to Settings -> Secrets -> Actions and notice the lack of VAULT_TOKEN_DOJO.

In a case that VAULT_TOKEN_DOJO is not added to a participant's repo, a request, including the affected repo names, can be made in slack at #forum-github:

Hi - we're in a GitHub Actions Workshop and some participant repos did NOT get assigned the VAULT_TOKEN_DOJO secret

Init Repo Workflow

Rare cases of the workflow init-repo.yml not executing have occurred.

The easist way to identify this is a lack of Initialize Repo execution in the repository Actions tab.

A symptom of this is if the participant repo fails to deploy to K8S. This can also be confirmed by looking at the values-dev.yaml fqdn entry. The fqdn should prefix to the repo name and not the template repo name.

Participants experiencing this may execute the Initialize Repo workflow via manual workflow dispatch directly.

Unable to access template or workshop repository

If a participant gets a 404 or other error accessing a repo, they should navigate to https://client.okta.com, update with client link authenticate there and select the GitHub Enterprise tile. Following this, they should be able to access the repos assuming they are a valid user for GitHub Enterprise.

Unable to access backstage documentation

If a participant cannot access backstage, this is not a blocker for the lab however, it is good for them to have future access to the content. Participants may request access via Service Now. For the application to access, they should enter Product Core Backstage Users. This request may take 24 hours to fulfill.