feat(api): implement account information endpoint #349
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As a Lacework Engineer that needs to migrate tools and integrations from APIv1 to APIv2, I need to have a mechanism to identify both authentication methods, So that I can start using both API versions and migrate endpoints gradually (not all at once). JIRA ALLY-369 Signed-off-by: Salim Afiune Maya <[email protected]>
afiune
added
feat
afiune
commented
Mar 22, 2021
api/account.go
Outdated
| client *Client | ||
| } | ||
|
|
||
| func (svc *AccountService) OrganizationInfo() ( |
There was a problem hiding this comment.
Every function inside the Go-Client has to have an action, this was missing:
Suggested change
| func (svc *AccountService) OrganizationInfo() ( | |
| func (svc *AccountService) GetOrganizationInfo() ( |
Signed-off-by: Salim Afiune Maya <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a Lacework Engineer that needs to migrate tools and integrations from APIv1 to APIv2,
I need to have a mechanism to identify both authentication methods,
So that I can start using both API versions and migrate endpoints gradually (not all at once).
JIRA ALLY-369
Signed-off-by: Salim Afiune Maya [email protected]