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.
Related
By default GitLab adds issue ID from branch name to the merge request description, see Merge requests to close issues:
Merge requests to close issues
To create a merge request to close an issue when it’s merged, you can either:
Add a note in the MR description.
In the issue, select Create a merge request. Then, you can either:
Create a new branch and a draft merge request in one action. The branch is named issuenumber-title by default, but you can choose any name, and GitLab verifies that it’s not already in use. The merge request inherits the milestone and labels of the issue, and is set to automatically close the issue when it is merged.
Create a new branch only, with its name starting with the issue number.
But I want to use a custom merge request description template, see Create a merge request template:
Create a merge request template
Similarly to issue templates, create a new Markdown (.md) file inside the .gitlab/merge_request_templates/ directory in your repository. Commit and push to your default branch.
Research
GitLab Flavored Markdown doesn't contain any markup for the issue ID from the branch name.
Markdown Style Guide for about.GitLab.com doesn't contain any markup for the issue ID from the branch name.
GitLab quick actions doesn't contain any action for the issue ID from the branch name.
Question
How to add issue ID from branch name to the merge request description template?
I'm looking for a similar problem, i see that Push Options can be a solution for this:
https://docs.gitlab.com/ee/user/project/push_options.html
for example:
merge_request.title="<title>" Set the title of the merge request.
merge_request.description="<description>" Set the description of the merge request.
It is true that this must be set up by the developer on the client side, but with git hooks and shell scripts, the content can be anything!
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
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
Currently I am using a DynamoDB instance for my social media application. While designing the schema I sticked to the "one table" rule. So I am putting every data in the same table like posts, users, comments etc. Now I want to make flexible queries for my data. Here I found out that I could use the #searchable annotation to create an Elastic Search instance for a table which is annotated with #model
In my GraphQL schema I only have one #model, since I only have one table. My problem now is that I don't want to make everything in the table searchable, since that would be most likely very expensive. There are some data which don't have to be added to the Elastic Search instance (For example comment related data). How could I handle it ? Do I really have to split my schema down into multiple tables to be able to manage the #searchable annotation ? Couldn't I decide If the row should be stored to the Elastic Search with help of the Partitionkey / Primarykey, acting like a filter ?
The current implementation of the amplify-cli uses a predefined python Lambda that are added once we add the #searchable directive to one of our models.
The Lambda code can not be edited and currently, there is no option to define a custom Lambda, you read about it
https://github.com/aws-amplify/amplify-cli/issues/1113
https://github.com/aws-amplify/amplify-cli/issues/1022
If you want a custom Lambda where you can filter what goes to the Elasticsearch Instance, you can follow the steps described here https://github.com/aws-amplify/amplify-cli/issues/1113#issuecomment-476193632
The closest you can get is by creating a template in amplify\backend\api\myapiname\stacks\ where you can manage all the resources related to Elasticsearch. A good start point is to
Add #searchable to one of your model in the schema.grapql
Run amplify api gql-compile
Copy the generated template in the build folder, \amplify\backend\api\myapiname\build\stacks\SearchableStack.json to amplify\backend\api\myapiname\stacks\
Remove the #searchable directive from the model added in step 1
Start editing your new template copied in step 3
Add a Lambda and use it in the template as the resolver for the DynamoDB Stream
Using this approach will give you total control of the resources related to the Elasticsearch service, but, will also require to do it all by your own.
Or, just go by creating a table for each model.
Hope it helps
It is now possible to override the generated streaming function code as well.
thanks to the AWS Support for the information provided
leaved a message on the related github issue as well https://github.com/aws-amplify/amplify-category-api/issues/437#issuecomment-1351556948
All you need is to run
amplify override api
edit the corresponding overrode.ts
change the code with the resources.opensearch.OpenSearchStreamingLambdaFunction.code
resources.opensearch.OpenSearchStreamingLambdaFunction.functionName = 'python_streaming_function';
resources.opensearch.OpenSearchStreamingLambdaFunction.handler = 'index.lambda_handler';
resources.opensearch.OpenSearchStreamingLambdaFunction.code = {
zipFile: `
# python streaming function customized code goes here
`
}
Resources:
[1] https://docs.amplify.aws/cli/graphql/override/#customize-amplify-generated-resources-for-searchable-opensearch-directive
[2]AWS::Lambda::Function Code - Properties - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-lambda-function-code.html#aws-properties-lambda-function-code-properties
I have been trying to delete multiple campaigns from Eloqua at a time using Postman. But I am not able to do. I don't see reference in the tool as well http://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAB/index.html#Developers/RESTAPI/REST-API.htm%3FTocPath%3D%2520Application%2520API%7C_____0.
Please let me know if deleting the multiple campaigns is possible.
It is not possible.
The link you provided mentions it's outdated, and a redirection link was available: http://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAC/rest-endpoints.html
Have a look at all the DELETE methods over there, and you will see that there is no provision for sending more than one id at a time.
Edit: You say you are using Postman. It is possible to perform repetitive tasks (like deleting mulitple campaigns) with different parameters each time by using Collections.
Edit 2:
Create an environment,
Type your url with the id as a variable, e.g.: xyz.com/delete/{id}
And send all the id values as a JSON or CSV file. They have given a sample JSON, you would simply have to provide your ids inside an array, e.g.:
[
{"id":1},
{"id":2},
{"id":3}
]