otty / dotfiles

All tools/SuiteCloud CLI for Node.js

SuiteCloud CLI for Node.js

suitecloud

A SuiteCloud SDK tool to manage SuiteCloud project components and validate and deploy projects to your account.

Detected by suitecloud | macOS, Linux, Windows |github.com

Sync it suitecloud.toml

Sync rules

What travels, what stays, what never leaves

SuiteCloud CLI for Node.js in your home directory Every rule on this page, by file

· cli/ Exclude

· log/ Exclude

· suitecloud-sdk-settings.json Exclude

· credentials_browser_based.p12 Never synced

· credentials_ci.p12 Never synced

· client_api_key.p12 Never synced

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/suitecloud.tomlThe file this page is generated from

id = "suitecloud"

name = "SuiteCloud CLI for Node.js"

homepage = "https://github.com/oracle/netsuite-suitecloud-sdk"

description = "A SuiteCloud SDK tool to manage SuiteCloud project components and validate and deploy projects to your account."

# The NetSuite mark Oracle ships as the icon of the SuiteCloud extension

# in this same repository.

icon = "https://raw.githubusercontent.com/oracle/netsuite-suitecloud-sdk/master/packages/vscode-extension/resources/extension_icon_dark.png"

detect = ["suitecloud"]

# Nothing to sync as content: a SuiteCloud project is described by files inside

# the project folder (project.json, manifest.xml, deploy.xml), and the only

# things the CLI writes to the home directory are the credential keystores

# below plus the local state carved out in `exclude`.

paths = []

# All from @oracle/suitecloud-cli 4.0.0, which resolves each of these against

# os.homedir() + FOLDERS.SUITECLOUD_SDK (".suitecloud-sdk"):

# src/core/sdksetup/SdkProperties.js getSdkPath() → .suitecloud-sdk/cli/<jar>

# — the Java SDK jar the CLI downloads on first run, a binary artifact.

# src/services/settings/CLISettingsService.js SDK_SETTINGS_FILEPATH →

# .suitecloud-sdk/suitecloud-sdk-settings.json — { isJavaVersionValid,

# vmOptions }, the cached result of probing this machine's JDK.

# The log directory is the `.suitecloud-sdk/log/` constant in the same SDK jar.

exclude = [

"~/.suitecloud-sdk/cli/",

"~/.suitecloud-sdk/log/",

"~/.suitecloud-sdk/suitecloud-sdk-settings.json",

]

# The account credentials are PKCS#12 keystores. The Node CLI hands credential

# work to the Java SDK jar it downloads (cli-2026.2.0.jar, from the

# sdkDownloadUrl in @oracle/suitecloud-cli's package.json); in that jar

# com/netsuite/ide/core/configuration/CoreConstants and

# com/netsuite/ide/core/credentials/repository/CredentialsFileProvider carry the

# constants "user.home", ".suitecloud-sdk", "credentials_browser_based.p12"

# (browser-based authentication, i.e. `suitecloud account:setup`) and

# "credentials_ci.p12" (machine-to-machine, `account:savetoken`).

# client_api_key.p12 is the third keystore, named in the CLI itself

# (src/ApplicationConstants.js FILES.CLIENT_API_KEY, joined with the same folder

# in src/utils/ClientAPIKeyObjectWrapper.js).

# Each keystore is encrypted with a random passkey the SDK keeps in the OS

# secure storage under "Oracle Netsuite: Account Credentials" / "Oracle Netsuite:

# Client API Key" (com/netsuite/ide/core/services/SecureStorageServiceImpl), or

# in a passkey environment variable for CI. A consumer that carries these files

# has to carry that passkey too, or re-authenticate on the new machine.

secret = [

"~/.suitecloud-sdk/credentials_browser_based.p12",

"~/.suitecloud-sdk/credentials_ci.p12",

"~/.suitecloud-sdk/client_api_key.p12",

]

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/suitecloud. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these keeps all credential files out.