search

SFDO-Tooling / CumulusCI

Python framework for building portable automation for Salesforce projects
http://cumulusci.readthedocs.io
BSD 3-Clause "New" or "Revised" License
363 stars 242 forks source link

Enable configuration for cci version update sources #3754

Open dcinzona opened 9 months ago

dcinzona commented 9 months ago

Feature Type

I'm interested in functionality that solves a current problem or limitation in how CumulusCI works.

Does your feature request solve a current problem?

Every time cci runs, it checks for updates against the hard-coded pypi.org website. This breaks when users are in environments without access to Pypi.org. It's just a nag, but it introduces clutter on the screen.

Describe the solution you'd like

Provide a feature to configure the source repo for checking for updates (or allow overriding the method with our own logic), or allow for disabling the auto-check.

Describe alternatives you've considered

Option 1: Create an environment flag to disable the automatic version update check

Option 2: Check channels in pip config and use those as the repo source.

Option 3: Create an environment flag that could contain the Pypi service URI

Option 4: Allow the user to create an extension / overriding method to allow for updates from custom sources.

Additional context

No response

osho-20 commented 9 months ago

would like to work on this

bdvorachek commented 6 months ago

One workaround would be to modify the cumulus_timestamp file that is used to keep track of when the last update check was run. On mac, this is located at ~/.cumulusci/cumulus_timestamp. Create or update that file with the value 1903842000, which should make the next update check happen in 2030.

cci version will still attempt to hit pypi, but running regular commands will skip any update check.