SASjs Config File

The CLI will autocompile macro dependencies that exist in the SASjs Macro Core library. These will also show in the documentation under 'node_modules'. If you'd prefer not to show these in the rendered docs, set this value to false.

The location to which the generated HTML SAS documentation is written. If missing, or left blank, the files will be written to the sasjsbuild/doc directory (default behaviour).

Provide the full URL to Data Controller so that sasjs doc can link the lineage diagram directly to the table viewer in Data Controller.
If left blank, or undefined, no links will be generated.

If true, sasjs doc will generate and display Data Lineage from Jobs and Services.

Configuration of the Doxyfile variables

If you are having certificate errors connecting to SAS, that cannot be properly resolved, try setting this value to true. This option only has an effect if rejectUnauthorized is not present.

Optionally override the trusted CA certificates. Default is to trust the well-known CAs curated by Mozilla. Mozilla's CAs are completely replaced when CAs are explicitly specified using this option.

Private keys in PEM format. PEM allows the option of private keys being encrypted. Encrypted keys will be decrypted with options.passphrase. Multiple keys using different algorithms can be provided either as an array of unencrypted key strings or buffers, or an array of objects in the form {pem: [, passphrase: ]}. The object form can only occur in an array. object.passphrase is optional. Encrypted keys will be decrypted with object.passphrase if provided, or options.passphrase if it is not.

If true the server will request a certificate from clients that connect and attempt to verify that certificate. Defaults to false.

If true the server will reject any connection which is not authorized with the list of supplied CAs. This option only has an effect if requestCert is true.

The name of the generated .sas program, which can be used to deploy the app using only SAS Studio. By default, this will be the name of the target.

The path to a .sas program that will be inserted at the start of the build .sas program (created when running sasjs build).

The path to a .sas program that will be inserted at the end of the build .sas program (created when running sasjs build).

These scripts are executed when running sasjs deploy. If the file is a .sas file, it is executed on the SAS server (Viya only). Otherwise it is executed locally. These scripts are run AFTER the deployment of the servicepack, if deployServicePack:true (Viya only).

If set to true the json pack produced by sasjs build will be auto-deployed to the appLoc of the specified target (creating all jobs and services in the SAS folder tree). Currently only Viya is supported for this flag.

When running sasjs compile, all programs in the folders defined in this array are compiled and placed into same-named folders under sasjsbuild/services. They will be compiled as services (so, with the service pre-code). Folders can be absolute, or relative to the sasjs folder.

The serviceConfig initProgram is a .sas file that is inserted at the start of every SAS service (after compiled macros and any macroVars, and before the service itself).

The serviceConfig termProgram is inserted at the end of every service as part of sasjs compile.

This object allows sasjs compile to insert specific macro variables at the start of every service. In this case, the code generated would be:

%let mac1=value;
%let mac2=42;

When running sasjs compile, all programs in the local folders defined in this array are compiled and placed into same-named folders under sasjsbuild/jobs. Folders can be absolute, or relative to the local project /sasjs folder.

The jobConfig initProgram is a local .sas file that is inserted at the start of every SAS Job (after compiled macros and any macroVars, and before the Job itself).

The jobConfig termProgram is inserted at the end of every Job as part of sasjs compile.

This object allows sasjs compile to insert specific macro variables at the start of every Job. In this case, the code generated would be:

%let mac1=value;
%let mac2=42;

An array of local folders. All assets placed in these folders are converted into web services - example file types could be png, svg, mp3, mp4, excel - anything really.

Provide the location of a square image, under the webSourcePath. Used as the display icon on the appStream page.

When set to true, frontend files saved in the webSourcePath will be converted to streaming services in the streamWebFolder in SAS.

This is the target SAS folder (relative to the appLoc) where the compiled web assets will be created.

Active when streamConfig is true. Is the source (or build, or dist) LOCAL folder, relative to the sasjs folder, which contains the frontend to be deployed. All assets (PNG, JS, CSS, HTML etc) are taken from here and converted to streaming services in streamWebFolder. In Viya and SAS 9, any relative URLS will be modified such that the links still work and the assets still load.

The name of the service containing the index.html for a streaming web app. Defaults to clickme and is always deployed under the appLoc/services SAS Folder.

The testConfig initProgram is a local .sas file that is inserted at the start of every Test (after compiled macros and any macroVars, and before the Test itself).

The testConfig termProgram is inserted at the end of every Test as part of sasjs compile.

This object allows sasjs compile to insert specific macro variables at the start of every Test. In this case, the code generated would be:

%let mac1=value;
%let mac2=42;

This program is the first to execute as part of 'sasjs test'. It does not contain the testInit, testTerm or macroVariables. It IS compiled.

The last program to execute as part of 'sasjs test'.