You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/DevGuide.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ You can deploy your branch to the staging environment where E2E tests can be run
82
82
83
83
If you want to run the C# scenario tests (make sure that you followed the getting started steps before), you will need to set some environment variables:
84
84
85
-
1. GITHUB_TOKEN : Get a github PAT from https://github.com/settings/tokens
85
+
1. GITHUB_TOKEN : See [instructions](#generating-github-pat-for-local-scenario-test-runs) below
86
86
1. DARC_PACKAGE_SOURCE : Get the path to the darc nuget package (which would be in `arcade-services\artifacts\packages\Debug\NonShipping\`, see below for getting this built)
87
87
1. MAESTRO_BASEURIS : Run ngrok and get the https url
88
88
@@ -173,3 +173,14 @@ You can disable the DNS Service by deleting `DnsService` from the add-on feature
173
173
]
174
174
```
175
175
If you change any settings in `ClusterManifestTemplate.json` run `Reset Local Cluster` from Service Fabric Local Cluster Manager to recreate the cluster configuration using the new settings
176
+
177
+
## Generating GitHub PAT for local scenario test runs
178
+
179
+
The GitHub scenario tests are ran against a dedicated organization - [`maestro-auth-tests`](https://github.com/maestro-auth-test). As such, a PAT with adequate permissions is required to run them locally.
180
+
181
+
To generate one, navigate to https://github.com/settings/tokens and select the `Fine-grained tokens` sub-menu on the navigation bar. The token should be generated with the following settings:
182
+
- Resource owner: `maestro-auth-test` (if this option is not available in the resource settings please ask the team to add you to the test organization)
183
+
- Repository access: `All repositories`
184
+
- Repository permissions: `Contents` - `Access: Read and Write`
185
+
186
+
This configuration will allow the tests to read and write to the test repos without any additional access to the org or the account itself.
result.ThrowIfFailed($"Failed to remove label {revisionTrafficWeight.Label} from revision {revisionTrafficWeight.RevisionName}. Stderr: {result.StandardError}");
0 commit comments