Hi @GerryNelson ,   Thank you for this interesting post full of details. Is there any plan to integrate this new image into a standard k8s deployment part of Viya Manifest (optionnaly) installed alongside Viya microservices ? A single pod deployment would suffice.   The k8s cluster UI manager (Lens, Openshift console) would then provide a http *serverless* shell terminal to run VIYA Cli commands in addition to the ssh/docker/Jumpbox approach.   One step further would be to provide a new (http Restful) plugin for Web Environment Manager with a ssh console running *into* the Viya CLI Pod  under the authenticated user own credentials. Adding some additionnal CLI to the image (kubectl, kustomize, git, jq) would enable to replace the need for an extra SSH/Linux terminal with full security including client/server authentication sequence (cli auth login) automatically performed.   Ronan ... View more

Hi @GerryNelson ,   Thanks for this operation guide, detailed and well-researched. This is not an easy task, for sure ! At the beginning, in the commands given for finding out the primary pod controller, there is an undefined environment variable SOURCE_CLUSTER  :     export SOURCE_CLUSTER=sas-crunchy-platform-postgres PRIMARY=$(kubectl get pod --selector="postgres-operator.crunchydata.com/role=master,postgres-operator.crunchydata.com/cluster=$SOURCE_CLUSTER" -o jsonpath='{.items[*].metadata.name}' | awk '{print $1}') echo Primary Crunchy POD is $PRIMARY kubectl exec -it $PRIMARY -c database -- bash SOURCE_CLUSTER being defined  in the following page : https://documentation.sas.com/doc/fr/sasadmincdc/default/calsrvinf/n00000sasinfrdatasrv000admin.htm?fromDefault=#p12n56ik0ke0l4n18799bspg87l1   Instead of following the steep path of DB switching here described, another option could be to re-install Viya from scratch a-A (internal) => B-b (external) using the export/import feature or Environment Manager or  (better) SAS Viya CLI transfer plugin with additional steps as following : (a) export all Postgres content to JSON package , (b) import the previous package.   Best Regards, Ronan   ... View more

Thanks for the update @AlexBeaver  ! ... View more

Thanks for reposting here @AlexBeaver , the original pages at the  Scalability & Performance Focus Area RND site are now offline, unfortunately : https://support.sas.com/rnd/base/index.html 🤔 ... View more

Excellent post ! Thanks for sharing. I wasn't aware that fs-based shortcuts might be enabled when filesystem access is switched off : it works like an AllowList access very easy to configure. ... View more

Thanks for sharing, @GemmaR . This is very interesting, especially the summary table at the end.  Thanks to David Weik's Change report with its filtering capabilities ( https://criptic.github.io/SAS-Whats-New/index.html ) I could trace back this Column feature to Viya Stable 202312 version (LTS can only refer to 202303 or 202310 bi-annual releases); next LTS in 2024 will also use this feature presumably. ... View more

Very important in practice, thanks a lot for sharing @BrunoMueller . ... View more

Hi @eddieleung305 ,   I have never tried changing the target caslib, but according to the importAssessment tool help below, there is an option to choose a specific caslib instead of public :   #./importAssessedContent --help NAME: importAssessedContent - This application imports published tables and reports, assessed by SAS 9 Content Assessment, residing on the file system to SAS Viya 4 by datamart. Please note that any previously imported content from the specified data mart type will be overwritten by this process. VERSION: 2023.05 USAGE: importAssessedContent [command options...] COMMAND OPTIONS: --help Shows help. --create-profile Specifies to prompt the user and create a SAS Viya command-line interface profile. Specifying this option will also result in the prompting for required values. --profile Specifies a SAS Viya command-line interface profile to use during import. Specifying this option will also prompt the user for login credentials. --sas-viya-path Specifies the fully-qualified path to the SAS Viya Command-Line Interface. --datamart-type Specifies what type of data mart to publish. Valid values are: profile, inventory, codecheck, i18n, summarizelogs, embatchcode, appusage --caslib Specifies the destination caslib. Default value: public --server Specifies the destination CAS server. Default value: cas-shared-default --version Displays the application's version. USAGE NOTES: This application makes use of the SAS Viya Command-Line Interface which can be downloaded from: https://support.sas.com/downloads/package.htm?pid=2512 After downloading the CLI, make sure to download its "CAS" plugin as well as its "transfer" plugin. See the "Additional Documentation" referenced below for more details. ADDITIONAL DOCUMENTATION: /app/list/tf/binaries/sas9ContentAssessment/assessment/doc/SASContentAssessment.pdf Since it looks feasible to change your reports data caslib, you can also try to move the Assessement VA reports once created in Public folder into another folder, secured, using VIYA Cli promote plugin :   https://documentation.sas.com/doc/fr/sasadmincdc/v_038/calpromotion/n0u4qkc837891vn1w8pd2rbqaxzb.htm   Changing outright the destination Folder doesn't seem to be possible with the ImportAssessment tool (v 2023.04) ; posting a feature request to the team in charge might be useful also ;-).   HTH, Ronan ... View more

Thank you @StuartRogers for sharing this important article. The requirement of having to onboard Directory-based Service accounts seem rather new, until now these kind of technical accounts had to be created in the underlying micro-service realm (kubernetes service accounts, sssd Linux accounts). Since Viya 4 pricing metric is usually the nominal user account, I would like to know if the new Service Account Users for Schedule is explicity  excluded from the user quota ? Once account does not make a large difference but, as you show in your examples, security models more complex (more realistic also) might imply more than one Service Account User for Schedule. ... View more

Thanks for sharing, @RPoumarede , this is very valuable information. K9s extra tip also much useful ! ... View more

Thanks for sharing, @XavierBizoux , excellent article, very informative. I wasn't aware how powerful and versatile the sasctl Python package can be for SAS Viya., as a complement to viya CLI, ARK ou pyviyatools.   ... View more

This is a welcome addition to the Content tool collection, very useful, thank you very much @GerryNelson . ... View more

Hi Michelle, this looks like a good idea. I was at the office (my client's) during last Bowl ;  wearing my SAS baseball cap would have been ludicrous ^^. I'll wear it next time. Cheers Ronan ... View more

Thanks for your answer @EdoardoRiva  and for the link also, this is clear. ... View more