Process for importing Egeria into Postman as listed in dojo is no longer functioning
Closed this issue · 3 comments
The current Egeria dojo documentation section for "Importing Egeria Postman data" (https://egeria-project.org/education/tutorials/postman-tutorial/overview/#create-a-new-workspace) lists a process that no longer functions. Postman has made updates (with possible bugs) that prevent users from importing the data the way it is described in the dojo. This will need to be updated for any new users to be able to successfully import Egeria into Postman.
The specific issue is that after selecting Import->Code Repository->Github (and authenticating) is that only organizations the user is a member of are available in the drop down list for 'Organization'.
Previously this could be overtyped with the desired repository, ie 'odpi' but this no longer works. (In this example I use 'apache' as I am not a member of the org, so it demonstrates the principle) . The field is now behaving as a filter rather than a seeded entry field
The documented approach is very useful as postman automatically scans the repo for postman collections & environments.
Note that it WILL work for anyone a member of the odpi organization, but this excludes anyone who has yet to become a contributor.
This is a change of behaviour. There are some issues open on postman that appear to touch on this.
The best hope would be that this is a temporary issue, and once reported postman will fix (we may also be able to find which version introduced this issue)
The alternative is to either
A) Import file URL
The user would need to know which URLs to point to - there is a fair list, those could be documented & cut/pasted into postman one at a time
B) Import from file/directory
Similar to above, but requires a git clone.
C) Suggest any user joins the org
The user could request to join odpi, and could have no specific permissions - but users may not want to do this when experimenting
D) Build process creates a composite collection
We could aggregate the required collections together perhaps? To make downlod/install easier?
I opened up a postman issue - postmanlabs/postman-app-support#11767
Suggest we see what they say. Hopefully it's a bug.
If not, we'll need to redo the docs, and or consider if we want to structure the postman data
Thanks @cjjaramillo for fixing. We can close this now. If I notice a feature status change on the postman issue we can revisit