...
Input Name | Input Code | Required | Description | ||
---|---|---|---|---|---|
Oracle SaaS FSM Account |
| No | The Oracle SaaS FSM account with all the required properties like instance URL, Username, and Password. | ||
Node Executable PathDelete if version already exists |
| No | An absolute path to a Node executable or its parent directory. If not given, node in path will be considered. @Since 6.5.0.16 | ||
Nodejs Version |
| No | Nodejs version. Installs node with the provided version. This input will be ignored if the input | ||
NPM Install Arguments |
| No | Allows to enter one or more arguments to npm install command. (Ex --no-optional). @Since 6.5.0.14 | ||
.npmrc |
| No | npm configurations entered as list of key = value parameters (e.g. loglevel=notice), one key value pair per line. @Since 6.5.0.15 All default npmrc configurations are listed when the command “npm config list -l” is run. Some examples are- 1.registry=https://registry.npmjs.org/ (Specifies the URL of the npm registry) 2.strict-ssl=false (Controls SSL certificate validation during HTTPS requests.) 3.proxy=http://your-proxy-url:port 4.loglevel=verbose (Sets the logging level for npm output (e.g., 5.production=true (Instructs npm to skip installation of devDependencies.) For more details, refer npm-config | npm Docs Also, when multiple .npmrc files are available, npm follows a specific hierarchy for merging these configurations. Such as Project-Specific > User-Specific >Global. For more details, refer https://docs.npmjs.com/cli/v10/configuring-npm/npmrc | No | Delete the extension version if the version being deployed already exists. @Since 6.5.0.20 |
Artifacts
This operation consumes artifacts from the artifacts repository.
...