Postman - How to move collections between Workspaces? - postman

I have multiple collections on the same Workspace on Postman. Unfortunately things are starting to get messy, to many Collections from different projects on the same place.
How can I move some Collections/APIs to new Workspaces?

Share a collection
To Workspace, select yours, and make sure you checked "Share collection and remove from this workspace"
Voila!
Note: Worked on version 7.34.0.

Just export the collection and import from another workspace.

There are several Ways to do that some of them are as follows
There is a workaround. Tested with Postman v6.1.4
Export your collection. Switch workspace. (Re-)import saved .postman_collection.json Postman will even ask you if you want to copy the collection (into the new workspace) or if you want to overwrite it (meaning move it to the new workspace)
OR
Delete needed collections from workspace
A > sync > go to trash >
and restore collections to workspace B.
Hopefully, trash feature is enabled by default.
OR
Sharing collections in another workspace
In the workspaces dashboard, select a collection and then click the Share button. The collection is visible in your target workspace.

I think the simplest and fasted way to do this is to Fork your Collection and select the new Workspace you want to fork it into.
If you "Move" your collection by Sharing, once you delete your collection from one Workspace it will also delete it from the other.
Moving a collection by deleting and restoring or exporting and importing, forces you to leave the app.
So, just fork it is fast and easy.

In Postman v9.10.0
Click the three dots on the right of the collection name and select the action Move.
In the next screen select the workspace you want to move your collection to and click the Move Collection button.
That's it.

One way that was quick and easy was using the browser (instead of the app).
First, go to Postman using the browser and sign in. Next, create a new workspace - Test-1. It also gives you the option to choose the type of workspace; Personal or Team.
After creation, you now have at least 2 workspaces: the default workspace, My Workspace, and Test-1. It will create and put you inside the new workspace. Using the Collections or Environments tab, click Add Collections/Environments to this Workspace. You are now asked to pick a source workspace and then choose all or as many collections and environments as needed and finally Add to this workspace.
Whichever collections/environments you selected will now be duplicated to the new workspace.
Currently, there's no option to delete a collection or environment from a source workspace while copying it over. You will have to manually navigate inside a workspace to delete duplicates.

Click the three dots on the right of the collection name

Related

How to create a collection inside a collection in postman

I have tried drag-dropping one request onto another but it doesn't work.
I expected this to work as moving a request from one collection to another can be achieved this way.
Is there a way to achieve this?
You can create Folders inside a collection
Select a collection > Click on View more actions > Add folder
This is done mostly to group endpoints with similar functionality/ common initial routes.
Ex: stackoverflow.com/questions, stackoverflow.com/questions/:questionId
You can create more than one folder inside a collection.

How to copy a request from one workspace to another in Postman?

How to copy a request from one workspace to another in Postman? The Duplicate option just creates a copy in the same workspace and collection.
I don't think there is a way to copy individual requests. You can however do it at the collection level.
If you click ... next to collection name, you'll get options to move or export.
Selecting move will give you an option to select the target workspace.
Selecting export will generate a json file. You can then import this json in the target workspace.

Postman save and lock (prevent editing) request / collection

In Postman, once you have created a request or collection and have fine tuned it, is there any way to lock it so as to make it read only so that it can't be accidentally altered?
Obviously I would need something to toggle it back to editable again!
Thanks in advance
I don't think there is a option to make a collection read only for admin ( the creator of the collection). Few of the way of avoiding unnecessary changes are:
if you can edit rights of other users within the workspace make
it view only for selected users inside the workspace.
Create a fork of the collection so that you revert back
Create a copy of the collection
Download collection as json file
Personally i prefere downloading collection as json as this keeps the workspace clean and tidy .
else:
i prefer creating inprogress workspace and final workspace and sharing completed collection to final workspace and deleting it from ingrogress workspace everytime i finish something.
If changes is required , i will work in inprogress workspace by creating a copy

GCP Data Catalog - ONE for all projects (of one and more orgs)

What is the best practice
to get a company wide (one or more organisations each with multiple folders and projects)
INTO one central and all metadata contained data catalog ?
(if "multiple orgs" is too complex than let's start with one)
I've put together a sample showing how to work with one organization.
The main ideia is to use a Tag Central Project, where you store the common resources, like Tag Templates, Policy Tags and Custom Entries that could be reused.
So you have:
Tag Central Project
List of Analytics Projects (Where you have the data assets)
Then the next thing is the user personas you would use, I'd suggest starting with:
Data Governors
Data Curators
Data Analysts
This google-datacatalog-governance-best-pratices GitHub repo contains the code which uses terraform to automatically set up those governance best practices I mentioned.
You can adapt those samples to work at folder or organization level by changing the terraform resources.

cctiddly change workspace URL

I'm using ccTiddly (using the TiddlyWiki) and I would like to change the URL of my workspaces. I am not sure how to proceed, I tried a first time and everything was corrupted.
The old URL is www.sub.mysite.com/wiki and the new one is www.mysite.com/wiki
I was thinking to move all the files from the FTP folder and then edit the database by removing the "sub" from all the URLs.
Will that work fine?
I only have 2 workspaces with few tiddlers each.
Thanks!
It will depend which version of ccTiddly you are using.
Take a look at the fields in the database. I think you should be able to make the change just by updating the workspace field on the tiddler table but check there are no other fields storing the workspace.
When you said it corrupted everything last time, what exactly do you mean?