This is a small video by Jake Snyder on how to access the public Mist Runner collections on Postman.
You can go to explore. You can search and say, I’m looking for Mist Systems. I want the Mist Systems public workspace. What you’ll see in here, there’s two collections. Cool part about this is you can click and say, create a fork. This is Jake SE demo. And this will make a copy just like you’re forking a repo in GitHub.
Cool part about that is that at any point in the future, if I update, you can say merge changes. And if I’ve made changes, it will ask you which of those changes you want to merge in. So you no longer have to download the JSON, import it again, and do those types of things. But just a quick demo, we can go through and run site creation on my personal org. You can go run. We’re going to pick a CSV file. Site creation all scenarios.
We can preview what all the sites it’s going to create. There’s a bunch of scenarios in this that I use for testing. So whether we’re going to skip geocoding. This one is to test some duplicates, whether we actually will create it. But if you run this, you’ll see that it creates sites. It airs out on some sites. We can look at the summary and see, well, I didn’t create one for one. I didn’t create one for four. But everything else was successful.
And typically, we’re failing because it was a duplicate site name. We aren’t going to create duplicate sites. And now, if I roll back to my site configuration and refresh, you’ll see there’s some new ones in here, the skip geocoding site. There are some troubleshooting ones. If you want to find out-of-compliance apps or you want to just go upgrade apps, not running a specific version, you can do that.
I also try to– there is a documentation button inside Postman. I’m not perfect, but I try to keep all of the documentation up to date in each particular runner. So if you want to see what environment variables I need to set or if you need to do things, the instructions are in each particular one.