-
Notifications
You must be signed in to change notification settings - Fork 2
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
FLAGINT-44-add-new-entries-api #13
base: master
Are you sure you want to change the base?
Conversation
… the default options
… soon when v3 APIs are release
…PI url to be stored as this.newUrl in EnvoyAPI
…Unit tests Added as well
… nested workObject object in its args.
… accept query params for filtering results.
…y, loginAsUser tests
…stallConfig() instead
this.baseUrl = process.env.ENVOY_BASE_URL || 'https://app.envoy.com'; | ||
this.newUrl = 'https://api.envoy.com/v1'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably call this something more descriptive than newUrl
, maybe baseApiUrl
and add an env var for it. Also, we should probably remove the v1
on it so that it's just the api.envoy.com domain.
this.baseUrl = process.env.ENVOY_BASE_URL || 'https://app.envoy.com'; | ||
this.newUrl = 'https://api.envoy.com/v1'; | ||
// External OAuth login url | ||
this.envoyAuthUrl = 'https://app.envoy.com/a/auth/v0/authorize?response_type=code'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are we planning to use this? Currently integrations payloads include an integrations scoped JWT and a user scoped JWT for making calls so most integrations will not need to call auth directly.
Style note, a url constant should not have parameters on it. The ?response_type=code
should be added in place when the url is used.
No description provided.