-
Notifications
You must be signed in to change notification settings - Fork 481
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
Remember authentication details with endpoint configuration #1526
Remember authentication details with endpoint configuration #1526
Conversation
60dd5d3
to
67ae3cf
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I'm having difficulties running it on Windows. |
We decided to not ship this with |
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.
As discussed, please perform the following changes:
- remove
keytar
for the moment - add a checkbox that must be checked by the users to confirm that credentials should be stored
- if checked, store credentials using our existing configuration mechanism
We may follow up on this PR in the future to add OS keychain support. |
This comment has been minimized.
This comment has been minimized.
76a245d
to
d52f479
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ed5fdae
to
29fc475
Compare
b2ab748
to
1380f36
Compare
3a87c1d
to
2e29877
Compare
9865634
to
e1d03cf
Compare
2e29877
to
ad3c0da
Compare
ad3c0da
to
35b6873
Compare
35b6873
to
5ca305d
Compare
* remember authentication details, if the user actively decides this * restore global endpoint configuration, as intended until it is properly addressed via #804 * refactor deployment tool, pulling out validation into separate component * pull out menu update functionality to be re-added at a later point in time, in a different place * deployment tool UI remains untouched Closes #1067
This is still not an optimal solution. What I'd personally like to end up with is something that just works without the need for modal implementors to care about it. It is up to future work on this topic to achieve this.
a0913ee
to
9e535b6
Compare
* test various untested specifics * assert executed fetches in curial code paths (authentication) NOTE: We still need proper assertions in some places. Right now we at least know that all executed code paths are not throwing.
9e535b6
to
54849e8
Compare
|
||
this.baseUrl = normalizeBaseURL(endpoint.url); | ||
|
||
this.authentication = this.getAuthentication(endpoint); |
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.
Really like this one, makes absolute sense 👍
componentWillUnmount() { | ||
this.mounted = false; | ||
componentDidMount() { | ||
this.connectionChecker.subscribe({ |
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.
Cool stuff, this makes the modal so much easier.
await this.saveDetails(tab, details); | ||
configuration = await this.saveConfiguration(tab, userConfiguration); | ||
|
||
if (action === 'save') { |
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.
Should be ok to keep it internally for future reference.
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.
Very good job in the refactorings! 🚀 This will definitely help us to improve the tool in the future. I even think it improves certain situations when it comes to finally include the start instance feature (cf. ConnectionChecker
). The test coverage should fit our needs for now.
One thing I could even think of, and what we discussed back on Wednesday, is to go one step further in "splitting up functionality into multiple modules" (like we did with the DeploymentConfigValidator
) and think about also splitting the UI (deployment config modal opening, showing notifications, rendering toolbar actions) and the business / service logic (performing deployments) of the DeploymentTool
.
For now, it works perfectly fine and nothing will hold us from creating further plugins (cf. the start instance feature), but I could think about having this as a substantial improvement in the future.
Good job at all 👍
Closes #1067
Add tests: