SailPoint SDK/CLI - Windows 10 cant run 'sail'

I’ve read every doc I can find on the subject of setting up the Windows environment for Sailpoint CLI/SDK tools.

after installation of the module:
(works) Get-module -ListAvailable PSSailPoint
(works) Get-Command -Module PSSailpoint

however it seems that when I run the basic command of “sail” …
nothing happens except for an error “sail: The term ‘sail’ is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.”

how is this fixed? (powershell 7, windows 10)

Thanks

Hello @wle831.

Welcome to the Developer Community :slight_smile:

As far as I am aware, the CLI and the SDK are two separate components. It seems you are installing the SDK.

To install the CLI, check out this guide: Command Line Interface | SailPoint Developer Community
Depending on how you install, you may need to add the executable to your windows PATH environment variable.

For information on the SDK, check out this guide: PowerShell SDK | SailPoint Developer Community

If you have any other questions, feel free to post them on this thread and I’d be more than happy to lend a hand. If you feel this or another post solves your problem, please mark that as a solution so others can easily find the help they need.

1 Like

Hey @wle831, welcome to the SailPoint Developer Community, and thanks for posting this question.

It looks like you are running into this error because sail is an application that you are trying to execute that PowerShell (and your entire computer) is not sure of the file path in which it is stored. To solve this, we need to add the folder containing the sail application and associated files to the Environment Path.

You can do this by executing the following command in PowerShell with administrative rights:

[Environment]::SetEnvironmentVariable("Path", $env:Path + ";C:\Program Files\SailPoint CLI\", "Machine")

Once completed, restart your PowerShell terminal and try again. Let me know how it goes!


References

2 Likes

Usually you have this error because you havent map this command like evironment variable or the installation was wrong. Try to reinstall or launch this command from own directory

1 Like

thank you Mr. Scott, this is the fix I was looking for.

2 Likes

cheers!

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.