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

Go Api for Catalog does not support ACL tokens #1893

Closed
mvanderlee opened this issue Mar 30, 2016 · 6 comments
Closed

Go Api for Catalog does not support ACL tokens #1893

mvanderlee opened this issue Mar 30, 2016 · 6 comments
Labels
type/bug Feature does not function as expected

Comments

@mvanderlee
Copy link

The api/catalog.go Register function does not support acl tokens.
The CatalogRegistration struct should likely have a WriteRequest field.

@slackpad
Copy link
Contributor

Hi @ddutch take a look at the WriteOptions parameter to Register() - you can use that to pass a token:

https://github.com/hashicorp/consul/blob/master/api/api.go#L63-L65

@mvanderlee
Copy link
Author

I did. But that doesn't work for the catalog. The rest Api documentation only mentions passing a write request object in there body, no parameter.

The write options object in Go gets translated to a URL parameter instead of Body.

@mvanderlee
Copy link
Author

@mvanderlee
Copy link
Author

There is either a bug in the Go api, or in the rest api endpoint.

@slackpad slackpad reopened this Apr 13, 2016
@slackpad slackpad added type/bug Feature does not function as expected easy labels Apr 13, 2016
@slackpad
Copy link
Contributor

Ah sorry about that. I'm thinking it is probably cleaner to teach the REST endpoint about the ?token= parameter to make it more inline with others than to add support for the WriteRequest on the API side.

@slackpad
Copy link
Contributor

This has been fixed in the register endpoint - #1738.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Feature does not function as expected
Projects
None yet
Development

No branches or pull requests

2 participants