-
Notifications
You must be signed in to change notification settings - Fork 1
/
action.yml
53 lines (51 loc) · 2.33 KB
/
action.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# action.yml
name: 'Data Theorem Mobile Secure'
description: |
Uploads your pre-production mobile app binaries to Data Theorem for scanning.
inputs:
DT_UPLOAD_API_KEY:
description: 'Data Theorem upload API key'
required: true
UPLOAD_BINARY_PATH:
description: >
Path to the app to upload.
You can use a glob pattern to indicate variable parts of the build's file name (for example, if the app's version number or build date is in the file name).
Examples of glob patterns:
- `app-*.apk` : search for any apk starting with `app-` in workspace root directory
- `**/app-*.ipa` : search for any ipa starting with `app-` in any subdirectory of the workspace
- `{,**/}app-debug*.*` : search for any file containing `app-debug` in root the directory or in any subdirectory of the workspace
If multiple files match the provided pattern all matching files will be uploaded. The pattern should not match more than 3 files.
required: true
USERNAME:
description: >
Username to be used for authenticated testing of the application. If provided, will override the previosly provided value.
required: false
PASSWORD:
description: >
Password to be used for authenticated testing of the application. If provided, will override the previosly provided value. Use of GitHub secrets is recommended.
required: false
COMMENTS:
description: >
Miscellaneous, free-form comments regarding the upload.
required: false
RELEASE_ID:
description: >
A custom ID associated with the binary being submitted, since the app version may not change very often.
It is recommended that you use a unique value for this, such as the CI/CD job ID.
If not set, Data Theorem will assign the binary a release_id.
required: false
PLATFORM_VARIANT:
description: >
The variant of the platform to use for scanning; Currently, the accepted value is
IOS_ON_MAC (scan an iOS build on an Apple Silicon Mac instead of on an iOS device, in order to exercise code paths that are specific to Macs.)
required: false
EXTERNAL_ID:
description: >
The external_id field represents your organization’s custom identifier for the app, if any.
required: false
runs:
using: 'node16'
main: 'main.js'
branding:
color: 'blue'
icon: 'arrow-up-circle'