You can use the Atlas Go SDK to fetch or modify data from the Atlas Admin API. The Atlas Go SDK is flexible because it accepts many different types of arguments.
To fetch data, you can execute the {Api}.{Operation}WithParams()
method:
// Surrounding code omitted for brevity
// 1. Calling API method
request := sdk.ProjectsApi.ListProjectsWithParams(ctx,
// 2. Passing a struct with all optional query parameters to the request
&admin.ListProjectsApiParams{
ItemsPerPage: admin.PtrInt(1),
IncludeCount: admin.PtrBool(true),
PageNum: admin.PtrInt(1),
})
// 3. You can also supply values in requests using individual methods
// This can be helpful when passing request objects to other methods.
projects, response, err := request.ItemsPerPage(10).Execute()
examples.HandleErr(err, response)
Alternatively, you can use the shorter {Operation}()
method with a builder pattern to supply all arguments:
// Surrounding code omitted for brevity
projects, response, err := sdk.ProjectsApi.ListProjects(ctx).ItemsPerPage(1).Execute()
Note: The Atlas Go SDK requires path parameters and they must be provided directly in the {Operation}()
method.
Note: The Atlas Go SDK supplies default values for both query and post objects.
Use the {Operation}()
method to perform modifications. For example:
// Surrounding code omitted for brevity
groupInvitationRequest := admin.NewGroupInvitationRequest()
resp, r, err := sdk.ProjectsApi.CreateProjectInvitation(context.Background(), groupId, groupInvitationRequest).Execute()
Each SDK request and response might contain read-only or write-only fields as identified by the documentation and the Go doc comments.
We use GoDoc comments to annotate fields as read and write only:
// Read Only field.
means that the field is included in responses but not in requests// Write Only field.
means that the field may be included in requests but not in responses
To learn more about using the SDK, see the basic example.
The Atlas Go SDK follows the Semantic Versioning (SemVer) specification. The versioning scheme used for this SDK is as follows: vYYYYMMDDXXX.Y.Z
, where:
YYYYMMDDXXX
represents the major version number. It includes the date of the Versioned API Resource Version that the SDK uses followed by three digits for other possible breaking changes.Y
represents the minor version number, indicating non-breaking iterations of the same Versioned API Resource.Z
represents the patch version number, indicating fixes in the SDK that do not affect users.
A major version increment signifies breaking changes in the SDK. The rules for major version increments are as follows:
- The major version must include the date of the Versioned API and three digits for other possible breaking changes.
- When a new Versioned API Resource Version is introduced, the SDK undergoes breaking changes and the version identifier is incremented. For example,
vYYYYMMDD
will becomev20300101
if a major version was released one year later. - If there are other significant breaking changes in the SDK that are unrelated to the Versioned API, increment the last three digits of the major version.
A minor version increment represents the Atlas Go SDK release based on iterations of the targeted Versioned API. When MongoDB adds new features or enhancements to the SDK that are backward-compatible with the previous minor version, increment the minor version.
A patch version increment indicates fixes and improvements in the SDK that do not affect users.
Let's break down the example version v20230201001.0.0
to understand its components:
- Major version:
v20230201001.0.0
v
: Indicates the start of the version number.20230201
: The date of the Versioned API version that this SDK is using, in the format ofYYYYMMDD
.001
starts from 001 and is incremented by 1 for every non-backward-compatible iteration targeting the specific API resource version.
The version v20230201001.0.0
represents the initial release of the Golang SDK library for the Versioned API dated February 1, 2023, with no other breaking changes, iterations, or fixes.