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

INTMDB-263: Added Private_link_endpoint_adl resource to go-client #271

Merged
merged 4 commits into from
Dec 16, 2021

Conversation

abner-dou
Copy link
Contributor

@abner-dou abner-dou commented Dec 14, 2021

Description

Added PrivateLinkEndpointADL resource to go-client to manage DataLake and Online Archive private link endpoints

Link to any related issue(s): INTMDB-263

Type of change:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Required Checklist:

  • I have signed the MongoDB CLA
  • I have added tests that prove my fix is effective or that my feature works
  • I have added any necessary documentation (if appropriate)
  • I have run make fmt and formatted my code

Further comments

@abner-dou abner-dou requested a review from a team as a code owner December 14, 2021 17:33
@abner-dou abner-dou requested review from gssbzn and removed request for a team December 14, 2021 17:33
// PrivateLinkEndpointsADLService is an interface for interfacing with the Private Link Endpoints ADL
// of the MongoDB Atlas API datalake and online archive.
//
// See more: https://docs.atlas.mongodb.com/reference/api/private-endpoints/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this link is not correct which leads me to a major issue here.

Given this statement about the go client lib README

The services of a client divide the API into logical chunks and correspond to
the structure of the Atlas API documentation at
https://docs.atlas.mongodb.com/api/.

You have two options

Add the methods to OnlineArchiveService (https://docs.atlas.mongodb.com/reference/api/online-archive/)
Or add the methods to DataLakeService (https://docs.mongodb.com/datalake/reference/api/datalakes-api/)

Even adding to both may be the correct thing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my bad, I copy from private_link but I forgot to change this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

already changed

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the link but that doesn't solve my main comment, let's not add a new service, let's add the method to OnlineArchiveService, DataLakeService or both

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I understand, but now my concern is, it is okay to use DataLakeService when you are using OnlineArchiveService and want to create a private_link?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happen if the API documentation for the private_link_endpoint for this gets a new section? you will need to "refactor" this services?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it okay to use DataLakeService when you are using OnlineArchiveService and want to create a private_link?

I say yes but up to you, remember one of the options is to add to both

What happen if the API documentation for the private_link_endpoint for this gets a new section?

We have a "no breaking changes" approach on the client unless strictly necessary, if the docs are moved around we should not move code around, we'll live with the choices made with what we knew today

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ready! I added this new methods on both datalake and online archive services

@abner-dou abner-dou requested a review from gssbzn December 14, 2021 21:44
Copy link
Collaborator

@gssbzn gssbzn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@abner-dou
Copy link
Contributor Author

@gssbzn I cannot merge due my access level, can you merge it, please?

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

Successfully merging this pull request may close these issues.

2 participants