Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import toxics from config.json #281

Closed
marcelothebuilder opened this issue Apr 24, 2020 · 3 comments
Closed

Import toxics from config.json #281

marcelothebuilder opened this issue Apr 24, 2020 · 3 comments

Comments

@marcelothebuilder
Copy link

Example, when importing this through docker:

[
  {
    "name": "es1",
    "listen": "[::]:9200",
    "upstream": "elasticsearch:9200",
    "enabled": true,
    "toxics": [
      {
        "name": "toxictest",
        "type": "latency",
        "stream": "upstream",
        "toxicity": 1.0,
        "attributes": {
          "latency": 15000,
          "jitter": 15000
        }
      }
    ]
  },

Using docker-compose.yml like this:

 toxiproxy:
    image: shopify/toxiproxy
    hostname: toxiproxy
    networks:
      - removed
    ports:
      - "9200:9200"
      - "9300:9300"
      - "5432:5432"
      - "8474:8474"
    command: -host=0.0.0.0 -config=/etc/config.json
    volumes:
      - ./toxiproxy/config.json:/etc/config.json

The specified toxic toxictest won't be imported. I think this is by design, but is there a nice way around this?

@mjpowersjr
Copy link

Hmm, this is exactly how I plan to use toxiproxy - did you ever find a solution?

@jonatan-ivanov
Copy link

Is there a maintainer around who could share some thoughts on this?

@miry
Copy link
Contributor

miry commented Oct 22, 2021

Duplicated #211

@miry miry closed this as completed Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants