Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Currently used destination connector in Admin section / Destinations tab #481

Closed
johnlafleur opened this issue Oct 2, 2020 · 0 comments · Fixed by #571
Closed

Currently used destination connector in Admin section / Destinations tab #481

johnlafleur opened this issue Oct 2, 2020 · 0 comments · Fixed by #571
Assignees
@jamakase
Labels
type/enhancement New feature or request
Milestone
v0.2.0

Comments

@johnlafleur
Copy link
Contributor

In an Admin section, we'd like the user to be able to manage the version of the destination connector they use.

  • as users can only have one destination connector for now, this list should only contain one connector.
  • With the text field, users should be able to change the version they use.
  • When clicking on the Docker image, it should open the corresponding web page in a new tab.
  • By default, the change button should be disabled, as the text field should have the current version name by default. When the user changes the version name in the text field, the Change button will become enabled
  • When changing the version, there should be a feedback (success or error)

Here is the design suggestion: https://www.figma.com/file/pO3Ob5W0yKUFOQzvg8TR3z/Airbyte?node-id=1%3A2476

@cgardens
@johnlafleur johnlafleur added type/enhancement New feature or request area/frontend labels Oct 2, 2020
@johnlafleur johnlafleur added this to the v0.2.0 milestone Oct 2, 2020
@jamakase jamakase mentioned this issue Oct 14, 2020
Merged
davydov-d added a commit that referenced this issue Sep 22, 2022
@davydov-d
#481 oncall source fb marketing: limit time range to 37 months
24c5de9
davydov-d added a commit that referenced this issue Sep 23, 2022
@davydov-d @octavia-squidington-iii
Source Facebook Marketing: limit time range to 37 months (#17027)
68cae56 
* #481 oncall source fb marketing: limit time range to 37 months

* source fb marketing: upd changelog

* #391 source facebook-marketing: retry on getting error 960

* source facebook marketing: format code

* auto-bump connector version [ci skip]

Co-authored-by: Octavia Squidington III <[email protected]>
robbinhan pushed a commit to robbinhan/airbyte that referenced this issue Sep 29, 2022
@davydov-d @octavia-squidington-iii @robbinhan
Source Facebook Marketing: limit time range to 37 months (airbytehq#1…
0ca7de8 
…7027)

* airbytehq#481 oncall source fb marketing: limit time range to 37 months

* source fb marketing: upd changelog

* airbytehq#391 source facebook-marketing: retry on getting error 960

* source facebook marketing: format code

* auto-bump connector version [ci skip]

Co-authored-by: Octavia Squidington III <[email protected]>
jhammarstedt pushed a commit to jhammarstedt/airbyte that referenced this issue Oct 31, 2022
@davydov-d @octavia-squidington-iii @jhammarstedt
Source Facebook Marketing: limit time range to 37 months (airbytehq#1…
e7f0612 
…7027)

* airbytehq#481 oncall source fb marketing: limit time range to 37 months

* source fb marketing: upd changelog

* airbytehq#391 source facebook-marketing: retry on getting error 960

* source facebook marketing: format code

* auto-bump connector version [ci skip]

Co-authored-by: Octavia Squidington III <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jamakase jamakase

Labels
type/enhancement New feature or request
Projects
None yet
Milestone
v0.2.0
Development

Successfully merging a pull request may close this issue.

Admin page airbytehq/airbyte
2 participants
@jamakase @johnlafleur