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

support for multiple instances of a single service #21

Open
shadeofblue opened this issue May 5, 2022 · 3 comments
Open

support for multiple instances of a single service #21

shadeofblue opened this issue May 5, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@shadeofblue
Copy link
Contributor

shadeofblue commented May 5, 2022

e.g.

nodes:
  http:
    payload: "nginx"
    entrypoint:
        ...
    network:
      "default"
    http_proxy:
      ports:
        - "80"
    cardinality: 5

vs

nodes:
  http:
    payload: "nginx"
    entrypoint:
        ...
    network:
      "default"
    http_proxy:
      ports:
        - "80"
    parametrize:
      - foo: "val"
        bar: 5
      - foo: "val2"
        bar: 2
@shadeofblue
Copy link
Contributor Author

nodes:
  http:
    payload: "nginx"
    entrypoint:
        ...
    network:
      "default"
    http_proxy:
      ports:
        - "80"
    ip:
      - "192.168.0.2"
      - "192.168.0.3"

@shadeofblue
Copy link
Contributor Author

ah, okay, I only now noticed the instances parameter in the GAP examples @stranger80

@shadeofblue
Copy link
Contributor Author

btw, an additional question: how should the ${services.db-service.network_node.ip} reference look if we wish to support multiple instances of services?

do we assume a single instance in the base form?
do we (always?) add an index, e.g. ${services.db-service[0].network_node.ip} ?

@stranger80

@johny-b johny-b added the enhancement New feature or request label May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants