Skip to main content

Postman–Working with data files

Instead of doing a manual cleanup of my local RabbitMQ cluster I decided to use the Management HTTP API and script the whole process.

I decided to use Postman and the collection runner data files support.

Let’s walk through the steps:

  • I started by creating a new Collection inside Postman:

  • Inside this collection I started adding DELETE requests to different objects(exchanges, queues,…) inside RabbitMQ

  • I used variables (recognizable with the double mustaches {{variableName}}) inside the URLs.
    • E.g. http://user:pw@localhost:15672/api/exchanges/%2F/{{exchange}}
  • These variables should be replaced by values from a JSON data file.
  • Create a JSON file containing a list of values. Unfortunately it is not possible to add the data file to your collection. So save it anywhere you want
    • Here is how the data file looked like for the above request:
  • Let’s now try to use the collection runner. Click on the Runner button at the top:

  • Select the collection you want to run on the left.

  • Also select a data file.
  • Click on the big blue run button to execute the requests in the collection. Parameters will be replaced using the values you’ve provided in the data file.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...