Skip to content

Latest commit

 

History

History
52 lines (31 loc) · 4.19 KB

Overview of Git-related Custom Steps.md

File metadata and controls

52 lines (31 loc) · 4.19 KB
Raw

Overview of Git-related Custom Steps

Description

The [SAS Studio Custom Steps] repository contains custom steps prefixed with "Git - ", which help you access Git (a popular source code management and repository service) functionality from within a SAS Studio Flow.

Such capability already exists through SAS functions as well as Git integration in SAS Studio.

Providing similar functionality through these Custom Steps helps you access source code and assets from within a SAS Studio Flow (which is basically a SAS program provided through low-code components). This enables portability and provides you Git version control, change tracking, and versatility in terms of choosing the analytics environment where you execute a set of SAS programs.

Here's a general idea:

The below image is an animated GIF.

Demonstrate Git Functions

Please go through this section to note the Requirements for all steps.

List of Custom Steps (this will expand as more contributors add more steps)

  1. Git - Clone Git Repo
  2. Git - Delete Local Repo
  3. Git - List Local Repo Changes
  4. Git - Stage, Commit, Pull and Push Changes

Which Git repositories are we talking about?

These Custom Steps can connect to and pull code from public and restricted access (subject to access rights) Git repositories on GitHub or GitLab. While not tested, it can also access code from a corporate Git repository (for example, gitlab.company.com) if the SAS Viya environment is within the same Virtual Private Network (VPN).

Requirements

  1. A SAS Viya 4 environment (monthly release 2022.11 or later) with SAS Studio Flows.

  2. Configure Viya environment for Git integration: This is typically carried out by the administrator of your Viya environment. Some suggested properties are available here.

  3. SSH key registration: Note that most Git repository hosting services (such as GitHub) require a SSH key to be registered with them and used for authentication. Ensure that you have followed instructions provided here. Here are instructions from GitHub on adding a SSH key to your GitHub account. It is recommended to use ECDSA SSH Keys when working with GitHub.

  4. Save SSH keys in Filesystem: Once you have your SSH keys generated, upload them to a folder within your filesystem. This is referred to within documentation here. To protect the integrity of your keys, ensure that only desired users have access to the folder where you are saving them to.

Documentation

  1. Understanding Git Integration in SAS Studio
  2. Using Git Functions in SAS
  3. Configuration Properties for Git Integration

Change Log

  • Version 1.1 (07MAR2023)

    • Changed doc URLs that were using .../v_xxx/... to using .../default/... so they resolve to the latest release of production documentation
    • Enhanced the list of custom steps to contain links to newly added Git-related custom steps

  • Version 1.0 (25JAN2023)

    • Initial version