-
Notifications
You must be signed in to change notification settings - Fork 0
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
CUS-377: oauthtoken: refactor to single fake LoadStorer implementation #21
Merged
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a9fa6db
CUS-377: oauthtoken: refactor to single fake LoadStorer implementation
jayconrod dd700b4
use real keyring
jayconrod 7223cee
Revert "use real keyring"
jayconrod 62e6f47
comment on why mock keyring is needed
jayconrod c317beb
fix review comments
jayconrod 76521d6
Merge branch 'main' into jay-refactor-loadstorer
jayconrod 5420cf7
fix merge error
jayconrod File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
// Copyright 2024 EngFlow Inc. All rights reserved. | ||
// | ||
// Licensed under the Apache License, Version 2.0 (the "License"); | ||
// you may not use this file except in compliance with the License. | ||
// You may obtain a copy of the License at | ||
// | ||
// http://www.apache.org/licenses/LICENSE-2.0 | ||
// | ||
// Unless required by applicable law or agreed to in writing, software | ||
// distributed under the License is distributed on an "AS IS" BASIS, | ||
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
package oauthtoken | ||
|
||
import ( | ||
"context" | ||
"fmt" | ||
|
||
"golang.org/x/oauth2" | ||
) | ||
|
||
// FakeLoadStorer is a test implementation of LoadStorer that stores tokens in | ||
// memory instead of the system keychain. | ||
type FakeLoadStorer struct { | ||
Tokens map[string]*oauth2.Token | ||
LoadErr, StoreErr error | ||
} | ||
|
||
var _ LoadStorer = (*FakeLoadStorer)(nil) | ||
|
||
func NewFakeLoadStorer() *FakeLoadStorer { | ||
return &FakeLoadStorer{ | ||
Tokens: make(map[string]*oauth2.Token), | ||
} | ||
} | ||
|
||
func (f *FakeLoadStorer) Load(ctx context.Context, cluster string) (*oauth2.Token, error) { | ||
if f.LoadErr != nil { | ||
return nil, f.LoadErr | ||
} | ||
token, ok := f.Tokens[cluster] | ||
if !ok { | ||
return nil, fmt.Errorf("%s: token not found", cluster) | ||
} | ||
return token, nil | ||
} | ||
|
||
func (f *FakeLoadStorer) Store(ctx context.Context, cluster string, token *oauth2.Token) error { | ||
if f.StoreErr != nil { | ||
return f.StoreErr | ||
} | ||
f.Tokens[cluster] = token | ||
return nil | ||
} |
Oops, something went wrong.
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.
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.
Do you think it's worth naming this
fake_test.go
so it ends up effectively testonly?Alternatively, if we want this in the binary - it could be named InMemoryStore or similar, since it seems like its a legitimate implementation
Side question on naming - I've always struggled with Go interface vs. struct naming convention (suffixing all interfaces with
-er
is sometimes limiting/awkward, avoiding-er
for struct types is also sometimes limiting, so I've historically follow the conventions sporadically depending on my mood). I notice here you've chosenFakeLoadStorer
for the struct type name - what's your approach to naming structs/interfaces?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.
I would if this were a single package, but this is needed in
cmd/engflow_auth/main_test.go
, so it needs to be exported from the library part of the package. I think that's okay: libraries sometimes provide fake implementations for other folks to test against.keyring
itself does this.Renamed to
FakeTokenStore
. Actually, I thinkLoadStorer
should be renamed toTokenStore
, though I haven't done so in this PR. Let me know if I should.I think the advice to name interfaces after verbs only works if the interface has one or two methods, and it's really generic, like
io.ReadCloser
. Anio.ReadCloser
could be basically anything, so it's hard to come up with a more descriptive name.If something has a specific purpose, it's better to name it after that. For example,
io/fs.FS
has one method,Open(string) (File, error)
.FS
is a much better name thanOpener
, andFile
is a much better name thanStatReadCloser
.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.
Agree 100% - I avoided naming it this since it didn't end in
er
, and I was making an extra effort not to deviate from convention. Makes sense about thefs.FS
naming - I guess the convention wasn't as strong as I had figured