paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 47 Packages Projects Releases Wiki Activity

integration support for harness p2-comments

Browse Source 
Signed-off-by: Calvin Lee <cjlee@ualberta.ca>
This commit is contained in:
Calvin Lee
2024-04-21 20:31:45 -06:00
parent 4750bf6622
commit d422716946
8 changed files with 31 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/harness/locations.md
+6 -6
View File
@@ -20,14 +20,14 @@ integrations:
harness:
- host: app.harness.io
token: ${HARNESS_CODE_BEARER_TOKEN}
apiKey: ${HARNESS_CODE_APIKEY}
```
Directly under the `harnessCode` key is a list of provider configurations, where you
can list the Gitea instances you want to be able to fetch
data from. Each entry is a structure with up to four elements:
Directly under the `harness` key is a list of provider configurations, where you
can list the Harness instances you want to be able to fetch
check out https://developer.harness.io/docs/platform/automation/api/add-and-manage-api-keys/ for more information
- `host`: The host of the Harness Code instance that you want to match on.
- `baseUrl` (optional): Needed if the Harness Code instance is not reachable at
the base of the `host` option (e.g. `https://app.harness.io`). This is the address that you would open in a browser.
- `username` (optional): The gitea username to use in API requests.
- `token` (optional): The password or api token to authenticate with.
- `apiKey` (optional): The apiKey to authenticate with.