-
Notifications
You must be signed in to change notification settings - Fork 43
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
Implement basic repo registration with gitlab #4464
Conversation
df53191
to
c430e61
Compare
013133b
to
19b449b
Compare
c430e61
to
f6a9206
Compare
cdbee74
to
9b7848a
Compare
2af2905
to
b80f945
Compare
9b7848a
to
dafe2ee
Compare
b80f945
to
26f1c61
Compare
627dbef
to
b72ed16
Compare
26f1c61
to
4d5cff9
Compare
4d5cff9
to
b3975ff
Compare
b3975ff
to
d53b666
Compare
9a6fad5
to
dcd6099
Compare
This adds the needed pieces for the GitLab provider to do entity registration. In the case of repos, this was the implementation of the repo lister trait. Signed-off-by: Juan Antonio Osorio <[email protected]>
dcd6099
to
5d2e102
Compare
}) | ||
if err != nil { | ||
return nil, fmt.Errorf("failed to create properties: %w", err) | ||
} | ||
|
||
return getByProps.Merge(outProps), nil |
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.
question (non-blocking): why is this merge no longer necessary?
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.
It's an implementation detail. It was necessary because I was forming merging what was incoming to what I'm forming here. Now, outProps
gets populated explicitly with everything that's needed, so I no longer needed the merge. It's just a little more efficient to not need to iterate over the incoming properties.
Summary
This adds the needed pieces for the GitLab provider to do entity
registration. In the case of repos, this was the implementation of the
repo lister trait.
Closes: #4331
Change Type
Mark the type of change your PR introduces:
Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist: