๐ŸŽ‰ Introducing the New Developer Community ๐ŸŽ‰

Yeah, Iโ€™m most interested in the SDK part. I donโ€™t have specific use cases really - Iโ€™d just like to avoid writing boiler-plate code for interacting with the API. A nice set of classes/commandlets/whatever with all of the HTTP/Response handling etc obfuscated would mean that when I do find things which the API can help with, the dev time will be much shorter. If thatโ€™s updated by Sailpoint and officially supported - great!

DM me if youโ€™d like any other clarification.

This PowerShell module isnโ€™t officially SailPoint created but has been really helpful for us:

1 Like

Hey @jallen,

Welcome to the community!

Just my two cents here, I donโ€™t often use PowerShell with IDN outside of operations on IQService hosts, but when I do I typically use the below fork.

Thanks @LukeHagar :hugs:
I did not want to mention it myself :wink:

1 Like

You can always self-promote here! Itโ€™s all about helping each other solve problems, there is no repercussion for doing that :slight_smile:

1 Like

Hey @jordan_violet ! Thanks for letting us know about how to use something like swagger-cli to dereference the API repo.

However, Iโ€™m using Homebrew and itโ€™s not recognizing swagger-cli as a package to install. Instead, I get the suggestion to install swagger2markup-cli:

Warning: No available formula with the name "swagger-cli". Did you mean swagger2markup-cli?
==> Searching for similarly named formulae...
This similarly named formula was found:
To install it, run:
brew install swagger2markup-cli

Guessing this is the same thing? :man_shrugging: Wondering if you know or anyone else does? Thanks!

@chris_wu swagger-cli is an NPM package. swagger-cli - npm.

Youโ€™ll need to download Node.js and NPM to use it.

You can use swagger-codegen with homebrew, or alternatively openapi-generator, which supports more features. I havenโ€™t had any luck yet with either one though :wink:

While these options exist, Iโ€™d strongly recommend allowing us the opportunity to build these tools for you, so you never have to generate them from the OpenAPI specification.

@chris_wu, what are you looking to generate from the specification?

Thanks for the clarification @colin_mckibben !

I was able to get both Node.js, NPM, then swagger-cli installed using Homebrew with instructions I found here: Install Node.js and npm using Homebrew on OS X and macOS |> Changelog

Install Node.js and npm with Homebrew

First, install Homebrew.

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Then run brew update to make sure Homebrew is up to date.

brew update

As a safe measure you should run brew doctor to make sure your system is ready to brew. Run the command below and follow any recommendations from brew doctor.

brew doctor

Next, add Homebrewโ€™s location to your $PATH in your .bash_profile or .zshrc file.

export PATH="/usr/local/bin:$PATH"

Next, install Node (npm will be installed with Node):

brew install node

To test out your Node and npm install, try installing Grunt (you might be asked to run with sudo):

npm install -g grunt-cli

If that worked then congratulations โ€” youโ€™ve installed Node.js, npm, and Grunt.

Using GitHub desktop, cloned the api-specs repo you posted @jordan_violet.

After installing from instructions above, then ran the following commands to dereference both collections and convert the yamlโ€™s into json files to import into Postman:

swagger-cli bundle -r <filepath>/GitHub/cloud-ui-search/api-specs/idn/sailpoint-api.beta.yaml -o <filepath>/sailpoint-api.beta.json

Then imported both sailpoint-api.v3.json and sailpoint-api.beta.json as new collections into Postman successfully.


@jordan_violet Apologies if you already answered this, but are there plans to publish a fully de-referenced Open API Spec? I am looking to consume these files in a tool, and a fully de-referenced single file YAML or JSON copy of each V3/Beta would be very useful

@chris_wu @LukeHagar Iโ€™m curious, what are some of your use cases with the specification?

We will be making the specification available again soon, but first we are looking to see what tools we can build so the community doesnโ€™t have to :slight_smile:

While I certainly appreciate all the hard work from the team and the improvements coming - it would be great if vendors (Iโ€™m looking at you, Microsoft) could update documentation without breaking links so often. Time to redo my bookmarks, but excited for the improvements.