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

updates for eft #3

Closed
wants to merge 1 commit into from
Closed

Conversation

levensailor
Copy link

Added

ADMIN

  • Resource Groups
  • Resource Group Memberships

USER

  • Attachment Actions
  • Devices
  • Place Services
  • Places
  • xAPI

@levensailor
Copy link
Author

You can wait until this is GA to merge. I'll monitor and if anything changes during the EFT, I'll cancel and resubmit with changes

@ObjectIsAdvantag
Copy link
Contributor

thanks Jeff

@ObjectIsAdvantag
Copy link
Contributor

hi Jeff, I am thinking to integrate the updates into distinct collections, depending on the purposes: user / admin but also bots or devices. Not sure if having all features in a single collection is that usefull, I have spread my Webex collections, currently I have:

  • Teams API V1 (user)
  • Admin API (admin) with /devices & /places
  • Cards (bot and user)
  • Devices (on-prem xAPI)
  • Devices Admin (on-prem xAPI)
  • Devices Cloud (/xapi) where I've put everything needed to activate a device too so /devices & /places (redundant)

thoughts @levensailor

@ObjectIsAdvantag ObjectIsAdvantag self-assigned this Sep 3, 2019
@ObjectIsAdvantag
Copy link
Contributor

So I just updated these existing postman collections:

  • Teams API V1 (user) with /attachment/actions
  • Admin API (admin) with /devices & /places
  • Cards (bot and user) with /attachment/actions

@levensailor Jeef, I looked at your proposal for /ResourceGroups & Memberships , these would need scripts added

@ObjectIsAdvantag
Copy link
Contributor

Also /places/services won't make it out of EFT.

So would suggest to pull the latest collection for admins and add /ResourceGroups & Memberships with scripts.
Creating issue #4 for that purpose if you feel like contributing , please do!

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.

2 participants