Skip to main content

How do I create and set GitHub variables?

External Action

The configuration described here takes place outside of Wayfinder.


Prerequisites​


Why do I need this configuration?​

In this section we're configuring the supporting variables in GitHub for the workflows needed to deploy your Wayfinder App to your ephemeral PR Preview and/or long-lived 'PROD' clusters.


Create and Set GitHub Workflow Variables​

Create and set the GitHub workflow variables below. Remember to adjust the variable values as needed for your application.

gh variable set WAYFINDER_WORKSPACE -r appvia/wf-example-app --body ws1
gh variable set WAYFINDER_SERVER -r appvia/wf-example-app --body https://api-wayfinder.myorg.io
gh variable set APP_NAME -r appvia/wf-example-app --body wfexampleapp
gh variable set APP_COMPONENT_NAME -r appvia/wf-example-app --body ui
gh variable set PR_PREVIEW_CLUSTER -r appvia/wf-example-app --body demo-envs
gh variable set LIVE_ENV_NAME -r appvia/wf-example-app --body prod

You can find the values for each variable as follow:

  • WAYFINDER_WORKSPACE and WAYFINDER_SERVER are displayed to you after you've created your Workspace Access Token
  • APP_NAME and APP_COMPONENT_NAME are the names that you have given to your application and container component when you created them
  • PR_PREVIEW_CLUSTER and LIVE_ENV_NAME are the names of existing clusters that you want to use for your PRs.

Resources​


What comes next?​