ACL support on agent force-leave endpoint

[andrake81]

Overview of the Issue

Can this PR be kindly reviewed? #15987

Reproduction Steps

Steps to reproduce this issue:

1. Create a cluster with ACL, integrated with Vault
2. agent/force-leave endpoint is ACL protected but passing a token will not help as it's not being utilized
3. View error:

< content-length: 113
< vary: Accept-Encoding
< x-consul-default-acl-policy: deny
<
* Connection #0 to host consul.server.net left intact
Permission denied: token with AccessorID 'dacd6887-313d-cb3f-1820-0994797e4375' lacks permission 'operator:write'```

[jkirschner-hashicorp]

Making sure I understand: the execution of the operation is ACL protected, but the token you provide in the HTTP request isn't actually passed along to the authorizer for that operation?

[andreikom]

Exactly @jkirschner-hashicorp

[pglass]

Hi, for informational purposes if others come across this issue: The api.Client supports setting a token used for all requests, so something like the following will work as a potential alternative in the meantime.

cfg := api.DefaultConfig()
cfg.Token = "<token>"

client, _ := api.NewClient(cfg)
err := client.Agent().ForceLeave("node1")

[pglass]

#15987 has merged so closing this issue.

The next release of the api package includes the ForceLeaveOptions method that accepts query parameters where the token can be specified:

cfg := api.DefaultConfig()
client, _ := api.NewClient(cfg)
err := client.Agent().ForceLeaveOptions("node1", api.ForceLeaveOpts{}, &api.QueryOptions{
     Token: "<token>",
})