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
|`version`||| Version of OrgFlow to install. Can be specified as major '1', minor '1.1' or patch '1.1.1'; latest matching version will be installed (omit to install latest available version). |
43
-
|`include-prerelease`||`"false"`| Set to 'true' to include prerelease versions when determining latest available version. |
44
-
|`skip-install`||`"false"`| Don't download and install OrgFlow (i.e. assume OrgFlow is already installed). |
45
-
|`license-key`|**Yes**|| Your OrgFlow license key (you can get one at https://www.orgflow.io/trial if you do not already have one). |
46
-
|`salesforce-username`||| Save username for connecting to production Salesforce org (stored on runner in encrypted form). |
47
-
|`salesforce-password`||| Save password for connecting to production Salesforce org (stored on runner in encrypted form). |
48
-
|`git-username`||| Save username for connecting to remote Git repository (not needed if connecting to a GitHub repository). |
49
-
|`git-password`||| Save access token or password for connecting to remote Git repository (use `secrets.GITHUB_TOKEN` if connecting to the current repository). |
50
-
|`git-committer-name`||`"OrgFlow Default Committer"`| Set name to use in committer signature when committing changes to Git repository. |
51
-
|`git-committer-email`||`"defaultcommitter@orgflow.io"`| Set email address to use in committer signature when committing changes to Git repository. |
52
-
|`stack-name`||| Name of OrgFlow stack to save credentials for (required when saving Salesforce or Git credentials). |
53
-
|`encryption-key`||| Encryption key to use when encrypting and decrypting Salesforce and/or Git credentials (omit to generate a new encryption key). |
54
-
|`log-file-name`||`"{C}-{T:yyyyMMdd-HHmmss-FFF}.log"`| Name (optionally tokenized) of OrgFlow diagnostic log files. |
55
-
|`log-level`||`"verbose"`| Verbosity level for OrgFlow diagnostic log files (verbose, debug, information, warning, error or fatal). |
56
-
|`upload-artifact`||`"true"`| Set to 'false' to disable uploading of all OrgFlow diagnostic log files and bundles during post-job processing. |
|`version`||| Version of OrgFlow to install. Can be specified as major '1', minor '1.1' or patch '1.1.1'; latest matching version will be installed (omit to install latest available version). |
43
+
|`include-prerelease`||`false`| Set to 'true' to include prerelease versions when determining latest available version. |
44
+
|`skip-install`||`false`| Don't download and install OrgFlow (i.e. assume OrgFlow is already installed). |
45
+
|`license-key`|**Yes**|| Your OrgFlow license key (you can get one at https://www.orgflow.io/trial if you do not already have one). |
46
+
|`salesforce-username`||| Save username for connecting to production Salesforce org (stored on runner in encrypted form). |
47
+
|`salesforce-password`||| Save password for connecting to production Salesforce org (stored on runner in encrypted form). |
48
+
|`git-username`||| Save username for connecting to remote Git repository (not needed if connecting to a GitHub repository). |
49
+
|`git-password`||| Save access token or password for connecting to remote Git repository (use `secrets.GITHUB_TOKEN` if connecting to the current repository). |
50
+
|`git-committer-name`||`OrgFlow Default Committer`| Set name to use in committer signature when committing changes to Git repository. |
51
+
|`git-committer-email`||`defaultcommitter@orgflow.io`| Set email address to use in committer signature when committing changes to Git repository. |
52
+
|`stack-name`||| Name of OrgFlow stack to save credentials for (required when saving Salesforce or Git credentials). |
53
+
|`encryption-key`||| Encryption key to use when encrypting and decrypting Salesforce and/or Git credentials (omit to generate a new encryption key). |
54
+
|`log-file-name`||`{C}-{T:yyyyMMdd-HHmmss-FFF}.log`| Name (optionally tokenized) of OrgFlow diagnostic log files. |
55
+
|`log-level`||`verbose`| Verbosity level for OrgFlow diagnostic log files (verbose, debug, information, warning, error or fatal). |
56
+
|`upload-diag-artifact`||`true`| Set to 'false' to disable uploading of all OrgFlow diagnostic log files and bundles during post-job processing. |
57
+
|`diag-artifact-name`||`orgflow_diag_${{ github.job }}_${{ github.run_attempt }}`| Name to use for the artifact when uploading OrgFlow diagnostic log files and bundles. |
57
58
58
59
## Outputs
59
60
@@ -231,4 +232,4 @@ This action enables and configures OrgFlow diagnostic logging, both for this act
231
232
232
233
You can override the naming of diagnostic log files using the `log-file-name` and `log-level` inputs. The `log-file-name` input supports several tokens you can use to base log file names on values only known at runtime. Please refer to the [logging section in our documentation](https://docs.orgflow.io/troubleshooting/logging.html) for more information about specifying log file names and log level.
233
234
234
-
This action also contains a post-job step that collects all OrgFlow diagnostic log files and bundles written throughout your whole job, and uploads them as an artifact on your workflow run named `OrgFlowDiagnostics`. This can be very useful during troubleshooting. If you wish to opt out of this behavior for any reason, you can do so by specifying `upload-artifact: "false"` as an input to this action.
235
+
This action also contains a post-job step that collects all OrgFlow diagnostic log files and bundles written throughout your whole job, and uploads them as an artifact on your workflow run named `orgflow_diag_<job>_<attempt>`. This can be very useful during troubleshooting. You can change the artifact name using the input `diag-artifact-name`. If you wish to disable the uploading of this artifact for any reason, you can do so by specifying `upload-diag-artifact: "false"` as an input to this action.
0 commit comments