Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update SaaS Connectivity "Connector Commands" docs with connector-spec commands #472

Open
hari-patel-sp opened this issue Jan 19, 2024 · 0 comments

Comments

@hari-patel-sp
Copy link
Contributor

Our current Connector Commands documentation for SaaS connectors (https://developer.sailpoint.com/idn/docs/saas-connectivity/connector-commands) only lists the human-friendly command names for the commands array that the connector-spec.json file contains. For example, we show that "Test Connection" is supported, but the value you must specify in the commands array is std:test-connection:

"commands": [ "std:test-connection", "std:account:list", "std:account:read", "std:entitlement:list", "std:entitlement:read", "std:account:update", "std:account:create", "std:account:enable", "std:account:disable" ],

Nowhere in our online documentation was I able to find the corresponding command value for all of our supported connector commands - I had to navigate through several SaaS connectors built by SailPoint Engineering in order to find the commands I was looking for.

One possible solution here would be to provide the system name next to the human-friendly name on the "cards" of the below page:
image

Additionally, an explicit callout for the value which should be included in your connector-spec.json file if you want to support that particular command. E.g., on the Account Create details page (https://developer.sailpoint.com/idn/docs/saas-connectivity/commands/account-create), state somewhere that you must provide std:account:create in the commands array.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant