This appears to be an unmaintained fork of the original code, which
lives elsewhere [1]. Kill it.
[1] https://github.com/cloud-init/cloud-init
Change-Id: I1f57197f1f67aa6adce152b5e4acc63a72277c6a
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
To solve the problem of "db type could
not be determined" on py34 we have to run first the py34 env to, then, run
py27. This patch puts py34 first on the tox.ini list of envs to avoid this
problem to happen.
Change-Id: I50f894062cf681a44fe7da2342a74b31898f47e8
Python 2.6 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it too.
Change-Id: I81d2a088bdf6f6052a45c4fabfdb32a662927098
--log-to-console will output messages at INFO and above to the
command-line. This is super-useful when running cloud-init from a
terminal, when you don't want to have to dig in a log file.
Change-Id: Ieb3db384b73441c19ef463649c94b04ffaac8026
This will allow us to actually have parameters passed in, which we'll
need for handlers with configuration options.
Change-Id: If105b8108d80b49b6da9e16c7520ddcee1f20c8f
pbr has issues invoking sphinx versions >1.3 (http://pad.lv/1379998)
The fix here is two-fold:
a.) no longer use 'pip install --pre'
I'd rather spend less time debugging failures due to new pip packages.
b.) shorten the list of requirements on sphinx as a result of 'a'
Since 1.3b* versions were pre, and we're no longer installing with --pre
we do not need to explicitly blacklist them.
At a future date when pbr is available with a fix, we can remove the upper
limit on sphinx.
Change-Id: I696fc3e4ef8803bbb2a95e34501d5330a64ab93c
This avoid modules that have been moved/removed from continuing to have
documentation generated for them. We use git clean to allow us to have
other files in there.
Possibly not an issue on the build hosts, but definitely irritating
locally.
Change-Id: I3403e8227913904a25b6a0866adfcc628d60419e
httpretty does not handle proxy well, but the need for http_proxy and
https_proxy is present if you're needing to install pip packages
behind a proxy.
Right now this will fail:
http_proxy=http://my.proxy/ tox --recreate
Example failures are in
UrlHelperWaitForUrlsTest.test_url_wait_for
it seems reasonable that we would never want proxy set when running tests
as we should never be doing real http traffic.
This just wraps our calls to nosetests with something that removes
the http_proxy friends.
Change-Id: I96585acaed0c8d70e1925b3859c85c87d1e07b2f
Fixing it should be a relatively minor change in nose, so I'll see if I
can get anywhere with that.
Change-Id: Ic883981d70bf6d4c344821fc45c70f1a0429ce7d
These will require a minimum of 90% coverage to pass.
Also remove unnecessary 'deps = {[testenv]deps}' lines; all [testenv:*]
targets use the values in [testenv] for any missing configuration
options.
Change-Id: Ifa311965c0329ce406cfb9e44660240574dacb4a
- put a brief description of license in LICENSE file
- put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0
- simplify the per-file header to reference LICENSE
- also, tox.ini: work around httpretty issue
Change-Id: I259ed23767472047da823c1a67085e47afc561d8
Add missing files and tweaks so that the automated
CI/flake8/pep8/docs/... and such work correctly.
Change-Id: I838b02bf0037569065b7c7914f4a68b92d7ebd6a
Stephen Finucane