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.

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

[EPIC] Source Gitlab to Beta #14152

Closed
15 tasks done
igrankova opened this issue Jun 27, 2022 · 5 comments · Fixed by #20511
Closed
15 tasks done

[EPIC] Source Gitlab to Beta #14152

igrankova opened this issue Jun 27, 2022 · 5 comments · Fixed by #20511

Comments

@igrankova
Copy link
Contributor

igrankova commented Jun 27, 2022

The main purpose of this issue is to track release progress for the connector.

According to checklist:

Acceptance criteria
  • Create a checklist document that should rbe placed on the Google Drive
  • Checklist filled up by engineering team
  • Collect and list all tech debt-related issues in the section below
  • Create/Revise MLP document and place it here
  • Move checklist to the unblockers team
  • Reviewed/Updated by unblockers team
  • Move checklist to the product team for review
  • Reviewed/Updated by product team
  • Update connector documentation according to the comments in the checklist
  • Certification completed
@girarda
Copy link
Contributor

girarda commented Dec 15, 2022

the gitlab connector is pinned to a very old version of the connector in cloud because it doesn't support oauth. Certifying it to beta will cause confusion because the certified version isn't used in cloud.

CC @YowanR

@YowanR
Copy link
Contributor

YowanR commented Dec 15, 2022

@davydov-d can you take a look, please?

@davydov-d
Copy link
Collaborator

@girarda @YowanR here is the PR implementing OAuth - #7506.
The plan was to merge the PR as soon as it gets unblocked (#3990 should be closed) -> certify to beta -> unpin in cloud. Am I missing something?

@tybernstein
Copy link
Contributor

I was made aware that this issue even though it is closed is not fixed and a user has encountered a similar issue. I noticed it appears as closed/completed in this [EPIC] and just wanted to make sure the team was aware that this was something that still needed to be addressed.
Screenshot 2023-01-20 at 9 54 07 AM

@davydov-d
Copy link
Collaborator

thanks @TBernstein4, I'll take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants