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

Service Discovery / Consul and jmespathquery to configure priorityGroup for pool members #610

Closed
paolobeta71 opened this issue May 24, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@paolobeta71
Copy link

Hi this request is to understand if I can use jmespathquery on Service Discovery working with Consul to parse additional information to set priorityGroup to pool members. We are currently supporting using jmespathquery the capability to configure custom ports on a pool member gathering this info from the jmespathquery.
Consul can also provides additional parameters in the form of meta information to set for example priorityGroup in a pool member. This snippet is an example:
.......
"Meta":{"application-version":"v1.0","configuration-version":"v1.2","external-source":"nomad","priority":"20",..............

with jmespathquery we can extract this information like SD does for ip or port, but I'm not sure if SD is also able to use a paramenter to configure the prorityGroup for a pool member. An example of my jmespathquery could be:
"jmesPathQuery": "[*].{id:Node.Address,ip:{private:Node.Address,public:Node.Address},port:Service.Port,priorityGroup:Service.Meta.priority}"
Can you please confirm if AS3-SD is able to configure priorityGroup for pool members or can only manage pool member name, ip and port?

@paolobeta71 paolobeta71 added enhancement New feature or request untriaged Issue needs to be reviewed for validity labels May 24, 2022
@mdditt2000
Copy link

Created Jira AUTOTOOL-3335 for PM tracking

@mdditt2000 mdditt2000 removed the untriaged Issue needs to be reviewed for validity label Jun 1, 2022
@sunitharonan
Copy link

This has been resolved in the 3.42.0 release of AS3.

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