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

feat(lucid-scim): user provisioning for create,disable (actions) and users(sync) #201

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

AndrewKaranja
Copy link
Contributor

@AndrewKaranja AndrewKaranja commented Jan 17, 2025

Describe your changes

Implemented the user provision for lucid-scim. This includes: create ,disable (actions) and users(sync)

Issue ticket number and link

EXT-314

Checklist before requesting a review (skip if just adding/editing APIs & templates)

  • I added tests, otherwise the reason is: Requires a Lucid Enterprise Account
  • External API requests have retries
  • Pagination is used where appropriate
  • The built in nango.paginate call is used instead of a while (true) loop
  • Third party requests are NOT parallelized (this can cause issues with rate limits)
  • If a sync requires metadata the nango.yaml has auto_start: false
  • If the sync is a full sync then track_deletes: true is set
  • I followed the best practices and guidelines from the Writing Integration Scripts doc

@AndrewKaranja AndrewKaranja self-assigned this Jan 17, 2025
Copy link

linear bot commented Jan 17, 2025

@AndrewKaranja AndrewKaranja marked this pull request as draft January 17, 2025 16:45
@AndrewKaranja AndrewKaranja changed the title feat (lucid-scim) : user provisioning for create,disable (actions) and users(sync) feat(lucid-scim): user provisioning for create,disable (actions) and users(sync) Jan 17, 2025
@AndrewKaranja AndrewKaranja marked this pull request as ready for review January 17, 2025 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant