GitLab

issue #10

We encouraged setting CSPP_GEO_AITF_ANCIL_TIMEOUT to a large value as a
workaround, so we can't rely on it being a good value.

https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/345

Also add some _getenv tests, including for the new functionality.

Rely on a non-routable IP address. Hypothetically might fail if some
layer is configured to return errors for such addresses. But it's a lot
easier that standing up (and maybe suspending?) a mini server.

Resolves
https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/345

Standardize help messages between aitf-data-for-run and aitf-update-cache https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/298

We need default of _2_ days cache since we start TOMORROW https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/298

Clarify --expiration is "unused" files, not "old" https://gitlab.ssec.wisc.edu/cspp_geo/cspp-geo-aitf/-/issues/298

Was removed over a month ago; just failed to remove obsolete
documentation

it was causing a test grief, also it looked bad

Just trying to prune __init__

This matches the old aitf-mirror behavior (and matching tests)

Relative to the dst passed to Downloader's update_cache/download_for_time

It was an overly clever hack. Manage summaries directly

Previously we relied on DownloadStats.report() to do it, but we don't
guarantee that will happen anymore. And really, when
Downloader.update_cache or Downloader.download_for_time finish, it's
done and should be marked as such.

It's no longer needed and it was an over-clever hack. #6

instead of magical logging.progress level. #6

DownloadStatistics.all_files() returns files that were downloaded or found
in the cache

Part of #5