See

https://spruce.mongodb.com/task/mongo_node_driver_next_rhel8_custom_dependency_tests_run_custom_csfle_tests_latest_73c1eae322205b171218f6a18b6cd98dbdeb9a27_f168e1328f821bbda265e024cc91ae54_24_09_17_18_02_35/logs?execution=0

This is notably different from our existing curl issue downloading node.js, prebuild is running into a timeout.

Use Case

As a Node.js engineer
I want to have stable setup tasks in CI
So that I know when something is actually failing

https://nodejs.org/download/release/v16.20.2/node-v16.20.2-headers.tar.gz

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
  • No direct impact by us. Users who may be installing from source and installing node.js everytime may suffer from the same issue if they do not use their own cached copy of node and headers or CDN.
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
  • None

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind
  • Node.js' CDN
  • DEVPROD-1224

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
  • TBD: Unknown
• Is there an opportunity for better cross-driver alignment or testing in this area?
  • No
• Is there an opportunity to improve existing documentation on this subject?
  • No

Acceptance Criteria

Implementation Requirements

• Remove the potential for failing to download Node.js header files from blocking CI

Testing Requirements

• None

Documentation Requirements

• None

Follow Up Requirements

• None