Loading...

XML

Word

Printable

JSON

Upstream Changes Summary:

Hide

DRIVERS-2710:
setup-atlas-cluster.sh and teardown-atlas-cluster.sh have been updated to ensure that they generate unique atlas clusters per task instead of per commit. both scripts now rely on the default evergreen expansion `task_id`.

If a driver is calling these scripts while using the `include_expansions_in_env` or `add_expansions_to_env`, no changes should be necessary. If a driver is not providing the `task_id` to the setup and teardown script, the config must be updated to pass this expansion as an environment variable for the scripts.

Show
DRIVERS-2710 : setup-atlas-cluster.sh and teardown-atlas-cluster.sh have been updated to ensure that they generate unique atlas clusters per task instead of per commit. both scripts now rely on the default evergreen expansion `task_id`. If a driver is calling these scripts while using the `include_expansions_in_env` or `add_expansions_to_env`, no changes should be necessary. If a driver is not providing the `task_id` to the setup and teardown script, the config must be updated to pass this expansion as an environment variable for the scripts.
Compass/DevTools Changes:
Not Needed

Documentation Changes:
Not Needed
Documentation Changes Summary:

Hide

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?

Show
1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

This ticket was split from DRIVERS-2710, please see that ticket for a detailed description.

split from

DRIVERS-2710 Atlas cluster setup script should create a unique cluster per-invocation, not per commit