-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: data connectors on the project page #3334
Conversation
You can access the deployment of this PR at https://renku-ci-ui-3334.dev.renku.ch |
f70273a
to
21bf381
Compare
7ddfdb6
to
e70872c
Compare
9173b4d
to
0ade890
Compare
2ff0f92
to
24ad645
Compare
24ad645
to
c55f56d
Compare
c55f56d
to
6907969
Compare
e21198e
to
21bf381
Compare
* refactor: move data connector api to its own folder
6907969
to
f9acac7
Compare
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.
Comments from manual testing:
-
When creating a new data connector from a project, the visibility is "private" by default, even on a public project.
-
When creating a data connector from a project page, using the "advanced mode" does not seem to work. I pasted the polybox config from
dev.renku.ch
but then the request sent to the backend only containedtype = webdav
and not the other fields.
client/public/crosshair.svg
Outdated
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.
Icons live in client/src/components/icons/
.
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.
Fixed in 4e0d010
isOpen: boolean; | ||
onDelete: () => void; | ||
toggleModal: () => void; | ||
} | ||
function DataConnectorDeleteModal({ | ||
function DataConnectorRemoveModal({ |
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'm confused here. Why do we try to cram to different features inside the same component? It would be simpler imo to have <DataConnectorRemoveModal>
and <DataConnectorUnlinkModal>
be two separate modals. Then further down in the actions components you decide to display or not the modal and button. The code is already deciding on which text to write there.
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.
Changed in 2b4eaab
client/src/features/dataConnectorsV2/components/DataConnectorView.tsx
Outdated
Show resolved
Hide resolved
client/src/features/dataConnectorsV2/components/DataConnectorView.tsx
Outdated
Show resolved
Hide resolved
import DataConnectorActions from "./DataConnectorActions"; | ||
import useDataConnectorProjects from "./useDataConnectorProjects.hook"; | ||
|
||
function ConfigurationKeyIcon({ configKey }: { configKey: string }) { |
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.
Note: This component replaces simple one liners, e.g. <Database className={cx("bi", "me-1")} />
. Therefore it does seem to increase complexity and reading.
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 are going to remove all the icon stuff anyway, I would prefer to leave this as is in this PR and fix it in a later PR.
…iew.tsx Co-authored-by: Flora Thiebaut <[email protected]>
Good point. I have fixed this in b1c7327.
I need to investigate this problem. |
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.
Great, thanks. Maybe we need to track the "advanced mode" issue.
I think this is the right way forward. I was able to create a data connector using advanced mode, so it does sometimes work. I have created an issue for this: #3349 |
Tearing down the temporary RenkuLab deplyoment for this PR. |
* feat: support for data connectors on user and group namespaces (#3315) * feat: set/edit secrets for data connectors (#3330) * feat: data connectors on the project page (#3334) * feat: support launching sessions with data connectors (#3346) BREAKING CHANGE: Requires renku-data-services version >= 0.xx.0 BREAKING CHANGE: Requires renku-notebooks version >= 0.xx.0 build: update to latest project api spec
* feat: support for data connectors on user and group namespaces (#3315) * feat: set/edit secrets for data connectors (#3330) * feat: data connectors on the project page (#3334) * feat: support launching sessions with data connectors (#3346) * minor: cosmetic improvements to data connectors (#3359) BREAKING CHANGE: Requires renku-data-services version >= 0.xx.0 BREAKING CHANGE: Requires renku-notebooks version >= 0.xx.0
* feat: support for data connectors on user and group namespaces (#3315) * feat: set/edit secrets for data connectors (#3330) * feat: data connectors on the project page (#3334) * feat: support launching sessions with data connectors (#3346) * minor: cosmetic improvements to data connectors (#3359) BREAKING CHANGE: Requires renku-data-services version >= 0.xx.0 BREAKING CHANGE: Requires renku-notebooks version >= 0.xx.0
/deploy renku-data-services=leafty/build-data-connectors