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.

Sign up for GitHub

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

Jump to bottom

Chainwatch can connect via multiaddr and token #47

Closed
2 tasks
placer14 opened this issue Aug 26, 2020 · 1 comment
Closed
2 tasks

Chainwatch can connect via multiaddr and token #47

placer14 opened this issue Aug 26, 2020 · 1 comment
Labels
kind/enhancement Improvement to an existing feature

Comments

@placer14
Copy link
Contributor

placer14 commented Aug 26, 2020 •
edited
Loading

Chainwatch requires access to the filesystem to find the API endpoint and token. Instead of requiring disk access, these values should be alternately configurable instead of requiring LOTUS_PATH or --repo flags.

Acceptance Criteria

  • On run subcommand, accept --api flag or LOTUS_API_INFO and FULLNODE_API_INFO env var as runtime option (format follows ./lotus auth api-info --perm read as <TOKEN>:<MULTIADDR>.)
  • On run subcommand, prefer --api flag values over values sourced by filesystem, if available. Error as usual w insufficient creds.
@placer14 placer14 added the kind/enhancement Improvement to an existing feature label Aug 26, 2020
@frrist frrist mentioned this issue Aug 27, 2020
Merged
@frrist
Copy link
Member

frrist commented Oct 6, 2020

visor accepts an API token as well, closing. (Also not sure why closing #3337 didn't' close this too)

@frrist frrist closed this as completed Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvement to an existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@placer14 @frrist