-
Notifications
You must be signed in to change notification settings - Fork 16
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
Make --secret override project config #308
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6098d79
Allow scoped secrets from --secret
macmv 43b9a37
Update config behavior to interpret --secret as an override
macmv 22d54b4
Fix tests
macmv 537b916
Add secret tests for parseFlag behavior
macmv e569010
Update eval tests to check new secret behavior
macmv 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,36 @@ | ||
export class Secret { | ||
// A fauna key, like `fn1234`. | ||
key: string; | ||
// Do we allow database scope? | ||
allowDatabase: boolean; | ||
// A database scope, like `["foo", "bar"]` | ||
databaseScope: string[]; | ||
|
||
constructor(opts: { key: string; databaseScope?: string[] }) { | ||
constructor(opts: { | ||
key: string; | ||
allowDatabase: boolean; | ||
databaseScope?: string[]; | ||
}) { | ||
this.key = opts.key; | ||
this.allowDatabase = opts.allowDatabase; | ||
this.databaseScope = opts.databaseScope ?? []; | ||
} | ||
|
||
static parseFlag(key: string) { | ||
if (key.length === 0) { | ||
throw new Error("Secret cannot be empty"); | ||
} | ||
return new Secret({ key, allowDatabase: !key.includes(":") }); | ||
} | ||
|
||
static parse(key: string) { | ||
if (key.length === 0) { | ||
throw new Error("Secret cannot be empty"); | ||
} | ||
if (key.includes(":")) { | ||
throw new Error("Secret cannot be scoped"); | ||
} | ||
Comment on lines
30
to
32
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. my understanding here is that we wouldn't allow scoped secrets in the |
||
return new Secret({ key }); | ||
return new Secret({ key, allowDatabase: true }); | ||
} | ||
|
||
buildSecret(opts?: { role?: string }): string { | ||
|
@@ -38,13 +52,20 @@ export class Secret { | |
* secret. This mutates `this`. | ||
*/ | ||
appendScope(scope: string) { | ||
this.databaseScope.push(...scope.split("/")); | ||
return this; | ||
if (this.allowDatabase) { | ||
this.databaseScope.push(...scope.split("/")); | ||
return this; | ||
} else { | ||
throw new Error( | ||
"Cannot specify database with a secret that contains a database" | ||
); | ||
} | ||
} | ||
|
||
clone(): Secret { | ||
return new Secret({ | ||
key: this.key, | ||
allowDatabase: this.allowDatabase, | ||
databaseScope: [...this.databaseScope], | ||
}); | ||
} | ||
|
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
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.
wondering if we should just have one parse method, could take as a parameter whether or not the key can be scoped. Could use both of these methods under the hood. looking at 2 methods parse vs parseFlag may not be clear which to use but if we had an explicit parameter,
allowScopedKey
or something, then it may make it a bit more clear.