Skip to content

APIBot: SDK update based on recent changes in Atlas API (v20240805) - DO NOT merge#576

Closed
svc-apix-Bot wants to merge 11 commits intov20240508-backport-2from
api-bot-update-v20240805-backport-cluster
Closed

APIBot: SDK update based on recent changes in Atlas API (v20240805) - DO NOT merge#576
svc-apix-Bot wants to merge 11 commits intov20240508-backport-2from
api-bot-update-v20240805-backport-cluster

Conversation

@svc-apix-Bot
Copy link
Copy Markdown
Collaborator

@svc-apix-Bot svc-apix-Bot commented Apr 1, 2025

Automatic update for MongoDB Atlas Go Client based on OpenAPI changes for API version 2024-08-05 (compare with v20240805005.0.0 release tag).
PR contains autogenerated changes for the MongoDB Atlas client.
This PR will not be merged. This was generated by making temporary updates to SDK generation workflow in #581

  • Added a branch protection rule for this branch.

Automated checks

  1. Compilation and unit tests
  2. Documentation style
  3. Transformation engine linting

Important Details

  1. If the build is failing please check the logs and fix the issues in the OpenAPI file (openapi/atlas-api.yaml)
  2. Do not attempt to manually fix any issues in the Golang code as all changes are automatically generated.
    Fixes should be applied to the OpenAPI file (openapi/atlas-api.yaml) or ./tools engine in a separate PR.

Manual Review Procedure

  1. Review changes in the OpenAPI file (openapi/atlas-api.yaml)
  2. If PR contains breaking changes, review ./releaser/breaking_changes/{release_version}.md file
  3. Approve and merge PR into the main branch
  4. After the merge automated release process will be triggered.

Troubleshooting

To skip release process after merge please revert changes from version.go file.
Release can be triggered by restoring changes in version.go.

@maastha maastha changed the base branch from v20240508-backport-2 to v20240508-backport April 1, 2025 22:45
@maastha maastha changed the base branch from v20240508-backport to v20240508-backport-2 April 1, 2025 22:46
// If reconfiguration is necessary to regain a primary due to a regional outage, submit this field alongside your topology reconfiguration to request a new regional outage resistant topology. Forced reconfigurations during an outage of the majority of electable nodes carry a risk of data loss if replicated writes (even majority committed writes) have not been replicated to the new primary node. MongoDB Atlas docs contain more information. To proceed with an operation which carries that risk, set **acceptDataRisksAndForceReplicaSetReconfig** to the current date.
AcceptDataRisksAndForceReplicaSetReconfig *time.Time `json:"acceptDataRisksAndForceReplicaSetReconfig,omitempty"`
AcceptDataRisksAndForceReplicaSetReconfig *time.Time `json:"acceptDataRisksAndForceReplicaSetReconfig,omitempty"`
AdvancedConfiguration *ApiAtlasClusterAdvancedConfiguration `json:"advancedConfiguration,omitempty"`
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

required change for CLOUDP-296222

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 3, 2025

This PR has gone 30 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

@github-actions github-actions Bot added the stale label May 3, 2025
@maastha maastha closed this May 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants