Ab-Initio - Air sanbox command. Part 2

Air sandbox commands:- 

1. air sandbox find [path] 

        [-up|-down] 

        [-sandbox] 

        [-relative] 

        [-project] 

<path>   Optional. Specifies the directory in which to start looking. Default is the current working directory.

-up | -down Optional. Default is -up. You can choose one:

-up specifies an upward search, toward the filesystem root, to see if the directory at path or any containing directory is a sandbox. Prints the path for the innermost containing sandbox, or fails if there is none. 

-down specifies a recursive downward search of the directory specified by path and its subdirectories. Prints the paths for all sandboxes found, or fails if no sandboxes are found.

-sandbox Optional. Specifies that the sandbox directory found should be listed (the default). Valid only with -up. Specify 

-sandbox only when you are specifying -relative and/or -project.  

-relative Optional. Specifies that the relative path from the sandbox directory to path should be printed. Valid only with -up. 

-project Optional. Specifies that the EME project the sandbox is associated with should be printed. Valid only with -up.

Example 1 

If you run the command without any options, it returns the sandbox directory — the same result if it were run with the -sandbox option. For example, the following command: 

air sandbox find

/home/<user>/test_sand

Running the command with -sandbox: 

> air sandbox find -sandbox

returns the identical path: 

/home/<user>/test_sand

<Server>:<user>:/home/<user>/test_sand/mp

Example 2 

Running the command with only -relative: 

air sandbox find -relative

returns the relative path to sand: mp

<server>:<user>:/home/<user>/test_sand/mp

Example 3 

Running the command with both -sandbox and -relative: 

air sandbox find -sandbox -relative

returns both the sandbox directory and the relative directory: 

/home/<user>/test_sand/mp 

2. air sandbox get-required-files [-force] [<path> ...]

Displays the set of files that are referenced by one or more files within a sandbox. Each line of the output contains the project path and relative filename separated by a tab character.

-force   Specifies that the command should continue even after an error is encountered (for example, if a required file cannot be found or if a URL contains an invalid parameter). In this case, the output may be incomplete.

-path     Path to one or more files in a sandbox. If no path is specified, displays the required files for all files in the sandbox.

3. air sandbox info <path> 

Displays information about a sandbox, or about files within a sandbox.

<path>    Path to a file or directory. The output includes sandbox and datastore information:

       air sandbox info  /home/<user>/test_sand

Filesystem Info:

   Path:             /home/<user>/test_sand

   Size:             8192

   Owner:            <user>

   Created:          2015-10-06 00:25:37

   Modified:         2015-10-06 00:25:37

   Accessed:         2015-10-06 01:00:36

   Permissions:      drwxrwxr-x

EME Datastore Info:

   Datastore URL:    file://<server>.<domain>.com/ai/repo/dev/dev_eme

   Branch:           main

   Project:          /Projects/dir1/dir2/dr3           

4. air sandbox lock <path>

                        [-set | -release | -break | -reset]

                        [-nocheck]

                        [-force] [-unbreakable] [-manual-release]

Performs lock operations on sandbox objects. Default operation is -set, to create a lock.

       <path>          Path to an object in a checked-in sandbox. If the object is a graph, the run script associated with the graph will also be locked.

       -set            Locks an object in a sandbox. Makes the file in the sandbox writable.

       -release        Releases the lock from an object in a sandbox. Makes the file in the sandbox read-only.

       -break          Breaks another user's lock on an object in your sandbox. After breaking it, you may lock the file with the air sandbox lock set command.

       -reset          Resets a lock broken by another user to unlocked state.

       -nocheck        Applicable if -set or -release specified. Causes the command to not do timestamp checking. Normally, air sandbox lock -set prevents you from setting locks on out-of-date files, and air sandbox lock -release prevents you from releasing locks on modified files.

       -force          Applicable if -set specified. Breaks another user's lock, if necessary, before setting lock.

       -unbreakable    Applicable if -set specified. Sets the lock to be unbreakable except by the EME administrator.

       -manual-release Applicable if -set specified. Causes the file to remain locked after the file is checked in.