[JAVA-5130] Atlas cluster setup script should create a unique cluster per-invocation, not per commit Created: 31/Aug/23  Updated: 12/Sep/23  Resolved: 12/Sep/23

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: PM Bot Assignee: Maxim Katcharov
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from DRIVERS-2710 Atlas cluster setup script should cre... Implementing
Upstream Changes Summary:

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.

Documentation Changes Summary:

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?


 Description   

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



 Comments   
Comment by Maxim Katcharov [ 12/Sep/23 ]

We use `add_expansions_to_env`, no changes needed.

Generated at Thu Feb 08 09:03:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.