-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't deploy .sas programs #991
Comments
Hi Chuck - correct, we support three categories of "job" - regular jobs (/jobs), web services (/services) and tests (/tests), all of which are deployed as "jobs" in Viya. We haven't built a feature for deploying SAS programs. We're happy to accept this as a feature request though. Would need to think about how we fit that into the framework - perhaps by having a A short term workaround might be to deploy as Jobs, then write an additional job (using SAS code) to read the content and deploy as a ".sas" program. This macro will list the jobs in a folder: https://core.sasjs.io/mv__getfoldermembers_8sas.html This macro will grab the code from a job: https://core.sasjs.io/mv__getjobcode_8sas.html And this macro can be used to create a SAS file (will also create any parent folders if needed): https://core.sasjs.io/mv__createfile_8sas.html |
Understood, thanks Allan. |
@ccastillo232 - we found a workaround for this (credit to @mblauw-sas) which would give you the functionality at the cost of a slightly longer deployment process. Basically, you create a Example config as follows:
To do the translation from Job to Studio Program you can make use of the following macros:
Creating the actual program is quite simple - just set up the fileref using the filesrvc engine, eg: filename outref filesrvc folderPath="&tgtappLoc/jobs/load" filename="jobx.sas"; Happy to jump on a call to assist with setup. |
I've found that when I cbd I can't actually specify a location of .sas files. I can only define jobs and services. For both, the assets are nested under a "jobs" or "services" folder. And both are deployed as job definitions, not as .sas files.
Is there a way I don't see to define a place for .sas files to be uploaded?
The text was updated successfully, but these errors were encountered: