- What has changed?
- Anaconda is moving the contents and services found on Anaconda.cloud to Anaconda.com, consolidating our platform into a single location.
- Why has this changed?
- Our goal is to simplify and streamline every user experience through centralized accessibility to products, services, and community.
- What will be different about my experience?
- Your experience will remain unchanged. The look and feel of Anaconda.com will resemble that of Anaconda.cloud, containing the same tools but with the added benefit of access to our full suite of services.
- How can we prevent customers from accessing the installers so we can better track usage?
- At this time, to prevent end users from downloading free installers, you can block repo.anaconda.com. However, please note that access to the Anaconda.com domain must be maintained for all users moving forward. Please note that in addition to blocking our installers, blocking repo.anaconda.com will block all free repos as well.
- Will my .condarc file break if it’s configured to anaconda.cloud?
- No action is required for your .condarc file. We have implemented automatic redirects from anaconda.cloud to anaconda.com. As long as you continue to allow access to anaconda.cloud, everything will function normally.
- Will I be able to access my custom channels if they are configured to anaconda.cloud in my .condarc file?
- Yes, you will have access to your custom channels.
- Does this update change any of Anaconda’s Terms of Service?
- No, if you were in compliance while accessing Anaconda.cloud, you will still be in compliance when accessing Anaconda.com (assuming all user actions remain the same).
- What actions do I need to take?
- If your organization currently blocks anaconda.com, you need to unblock it and add it to your allow list.
- Will this affect our SSO setup?
- SSO will continue to work as expected.
- Will my group or role settings change?
- No changes will be made to group or role settings as part of this domain change.
