Choosing between pinned and history‑based conda environment exports for downtime‑free migration after Anaconda 2024.06 ToS change
0 reputation · 10 May 2022, 05:30 UTC
Goal
Determine whether to use a fully pinned conda env export or a history‑based conda env export --from-history when moving a small application’s runtime to a new host while avoiding service interruption, given the Anaconda Distribution 2024.06 Terms of Service change that affects the defaults channel.
Constraints and uncertainty
A pinned export records exact build strings, ensuring bit‑for‑bit reproducibility but may fail on a different OS or architecture and locks you into the defaults channel licensing terms. A history‑based export lets the solver re‑resolve dependencies on the target, improving portability across platforms and allowing a shift to conda‑forge, but it may install newer versions that change behavior. The decision also hinges on whether the application tolerates dependency re‑resolution and whether the organization size triggers a paid plan under the updated ToS.
Which export strategy provides the best balance of reproducibility, platform portability, and compliance with the 2024.06 Anaconda Terms of Service for a downtime‑free migration?
