Global Variables

[camilamaia]

Global Variables

Enable the possibility to have global variables. Sometimes we need to access a variable from outside the scope, for example:

endpoints:
  - name: owner
    headers:
      Authorization: ${OWNER_TOKEN}
    requests:
      - name: register a book
        path: register/book
        method: post
        body:
          title: My Little Book
          author: John P.
        vars:
          book_id: ${{ request.json()["data"]["id"] }}
      - ...
      - ...
  - name: client
    headers:
      Authorization: ${CLIENT_TOKEN}
    requests:
      - name: rent a book
        path: rent/book/${book_id}
        method: POST
      - ...
      - ...

It would be nice to have a way to store book_id globally. Currently, the example above wouldn't work because the second request is not in the same scope as the first one.

[gillianomenezes]

Hi @camilamaia! Can I assign it to myself?

[camilamaia]

@gillianomenezes yes sure!!

[BrunoPontesLira]

Hi.
It is already running?

I am trying:

endpoints:
  - name: Cliente Credentials
    path: https://cloud.ihf
    endpoints:
      - name: GET access_token
        requests:
          - name: credencial
            path: api/oauth/token
            method: POST
            headers: {
              'x-x-correlationID': xxxxxxx,
              'x-x-flowID': xxxxxxxxxx,
              'User-Agent': Apache-HttpClient/4.5.5 (Java/11.0.5),
              'Content-Type': application/x-www-form-urlencoded
            }
            body: "xxxxxxxxxxxx"
            vars:
              access_token: ${{ response.json()['access_token'] }}
            tests:
              - name: Status code = 200
                assert: ${{ response.status_code == 200 }}

  - name: Titular
    path: https://mbi.cloud.ihf
    endpoints:
      - name: GET access_token
        requests:
          - name: credencial
            path: seguranca/v1
            method: POST
            headers: {
              'x-x-correlationID': xxxxxxxxxxxxx,
              'x-x-flowid': xxxxxxxxxxx,
              'x-x-apikey': xxxxxxxxxxxxxxxxx,
              'Authorization': ${access_token},
              'Content-Type': application/json
            }
            tests:
              - name: credencial status code = 200
                assert: ${{ response.status_code == 200 }}

[camilamaia]

@BrunoPontesLira not yet. There is a PR opened for it, but we did not merge it: #328. We need to test it first and ensure it works properly.

[camilamaia]

Actually, the PR #328 does not solve it, my bad. It only makes it possible to create vars at endpoint level. This is still an open issue

[gabrieltron]

I'd like to work on this issue, but since it's a non-simple change I'd like to discuss if you already have an intended approach to solve this problem. I was reading through the yaml specification and it says keys don't have a specific order. Considering that, we couldn't just run request nodes without ordering them. The way I'm thinking to approach the issue is building a dependency graph of request nodes, and we execute nodes without dependencies or with solved dependencies.

What are your thoughts?

[gabrieltron]

Ok, I admit that the first suggestion was the first thought without deeply studying the code hahaha
After doing that, I have a suggestion that I believe better fits with the tree-like structure, and it is much simpler. Looking forward for your feedback :D