SASJS-CLI¶
The SASjs Command-Line-Interface is a swiss-army knife with a flexible set of options and utilities for Dev Ops on both SAS 9 and Viya.
Core functionalities:
- Creation of a SAS GIT repository in an 'opinionated' way
- Compilation each service, including all the dependent macros / macro variables and pre / post code
- Build - creation of the master SAS deployment, including build macros, macro variables, and pre/post code
- Deployment - execute an array of local scripts and remote SAS programs to create your app on the SAS Server
There is also a feature to let you deploy your frontend as a service, bypassing the need to access the SAS Web Server.
Commands¶
Command | Description |
---|---|
add | Provides a series of prompts used to define a SAS target along with the relevant connection details (if SAS Viya) |
build | takes all of the input jobs and services and creates a build pack |
cbd | A shortcut to compile, build and deploy your project with one command! |
compile | Extracts all the dependencies and input programs for each service / job and includes them in a single file ready for deployment |
context | List, export, create, edit, and delete SAS Compute contexts |
create | Initialise a SASjs repository, either in plain form or using a range of templates |
deploy | Perform the actual deployment of a SASjs project into SAS 9 or Viya |
doc | Generate HTML documentation based on the Doxygen headers used in the SAS Macros, Programs, Jobs & Services. |
folder | Management of logical Viya folders |
job | Manage & Execute SAS Jobs |
lint | Lint your SAS code and identify commmon problems / undesirable coding practices |
request | Execute SASjs web services from the commandline |
run | Run arbitrary SAS code in a Viya Compute Session, directly from the terminal (or commandline session) |
servicepack | The SASjs Service Pack is a collection of services and folder objects. The servicepack command lets you deploy them easily |
flow | SAS job scheduler that takes a JSON file as input, and submit all the jobs sequentially, logging the results to an output CSV file |