upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-06-04 06:15:36 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
certbot/certbot-dns-route53/setup.py

59 lines
1.9 KiB
Python
Raw Permalink Normal View History

Remove unneeded sys import (#5873) * Remove unneeded sys import. Once upon a time we needed this in some of these setup.py files because we were using sys in the file, but we aren't anymore so let's remove the import. * use setuptools instead of distutils
2018-06-04 18:04:56 -04:00
from setuptools import setup
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
from setuptools import find_packages
Bump version to 0.30.0
2018-12-05 13:57:46 -05:00
version = '0.30.0.dev0'
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
Break lockstep between our packages (#5655) Fixes #5490. There's a lot of possibilities discussed in #5490, but I'll try and explain what I actually did here as succinctly as I can. Unfortunately, there's a fair bit to explain. My goal was to break lockstep and give us tests to ensure the minimum specified versions are correct without taking the time now to refactor our whole test setup. To handle specifying each package's minimum acme/certbot version, I added a requirements file to each package. This won't actually be included in the shipped package (because it's not in the MANIFEST). After creating these files and modifying tools/pip_install.sh to use them, I created a separate tox env for most packages (I kept the DNS plugins together for convenience). The reason this is necessary is because we currently use a single environment for each plugin, but if we used this approach for these tests we'd hit issues due to different installed plugins requiring different versions of acme/certbot. There's a lot more discussion about this in #5490 if you're interested in this piece. I unfortunately wasted a lot of time trying to remove the boilerplate this approach causes in tox.ini, but to do this I think we need negations described at complex factor conditions which hasn't made it into a tox release yet. The biggest missing piece here is how to make sure the oldest versions that are currently pinned to master get updated. Currently, they'll stay pinned that way without manual intervention and won't be properly testing the oldest version. I think we should solve this during the larger test/repo refactoring after the release because the tests are using the correct values now and I don't see a simple way around the problem. Once this lands, I'm planning on updating the test-everything tests to do integration tests with the "oldest" versions here. * break lockstep between packages * Use per package requirements files * add local oldest requirements files * update tox.ini * work with dev0 versions * Install requirements in separate step. * don't error when we don't have requirements * install latest packages in editable mode * Update .travis.yml * Add reminder comments * move dev to requirements * request acme[dev] * Update pip_install documentation
2018-03-05 12:50:19 -05:00
# Remember to update local-oldest-requirements.txt when changing the minimum
# acme/certbot version.
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
install_requires = [
Use greater than or equal to in requirements. (#6117) * Use greater than or equal to in requirements. This changes the existing requirements using strictly greater than to greater than or equal to so that they're more conventional. * Use >= for certbot-postfix. Despite it previously saying 'certbot>0.23.0', certbot-postfix/local-oldest-requirements.txt was pinned to 0.23.0 so let's just use certbot>=0.23.0.
2018-06-28 13:55:21 -04:00
'acme>=0.25.0',
Break lockstep between our packages (#5655) Fixes #5490. There's a lot of possibilities discussed in #5490, but I'll try and explain what I actually did here as succinctly as I can. Unfortunately, there's a fair bit to explain. My goal was to break lockstep and give us tests to ensure the minimum specified versions are correct without taking the time now to refactor our whole test setup. To handle specifying each package's minimum acme/certbot version, I added a requirements file to each package. This won't actually be included in the shipped package (because it's not in the MANIFEST). After creating these files and modifying tools/pip_install.sh to use them, I created a separate tox env for most packages (I kept the DNS plugins together for convenience). The reason this is necessary is because we currently use a single environment for each plugin, but if we used this approach for these tests we'd hit issues due to different installed plugins requiring different versions of acme/certbot. There's a lot more discussion about this in #5490 if you're interested in this piece. I unfortunately wasted a lot of time trying to remove the boilerplate this approach causes in tox.ini, but to do this I think we need negations described at complex factor conditions which hasn't made it into a tox release yet. The biggest missing piece here is how to make sure the oldest versions that are currently pinned to master get updated. Currently, they'll stay pinned that way without manual intervention and won't be properly testing the oldest version. I think we should solve this during the larger test/repo refactoring after the release because the tests are using the correct values now and I don't see a simple way around the problem. Once this lands, I'm planning on updating the test-everything tests to do integration tests with the "oldest" versions here. * break lockstep between packages * Use per package requirements files * add local oldest requirements files * update tox.ini * work with dev0 versions * Install requirements in separate step. * don't error when we don't have requirements * install latest packages in editable mode * Update .travis.yml * Add reminder comments * move dev to requirements * request acme[dev] * Update pip_install documentation
2018-03-05 12:50:19 -05:00
'certbot>=0.21.1',
Make it work as certbot-route53
2016-10-04 09:20:12 -04:00
'boto3',
route53: update setup.py to follow repo conventions (#4731) This change updates the setup script for the route53 plugin to more closely match conventions from other packages in the repository. Notable changes: * The version number is bumped to match the rest of Certbot. * The package now requires a matching version of ACME and core Certbot. * Contact information is updated. * Additional versions of Python are listed.
2017-05-26 17:44:05 -04:00
'mock',
Remove min version of setuptools (#5617)
2018-02-23 16:26:11 -05:00
'setuptools',
route53: update setup.py to follow repo conventions (#4731) This change updates the setup script for the route53 plugin to more closely match conventions from other packages in the repository. Notable changes: * The version number is bumped to match the rest of Certbot. * The package now requires a matching version of ACME and core Certbot. * Contact information is updated. * Additional versions of Python are listed.
2017-05-26 17:44:05 -04:00
'zope.interface',
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
]
setup(
route53: rename to match other DNS plugins (#4747) This change renames certbot-route53 to certbot-dns-route53 and updates the package's setup.py file to maintain backwards compatibility. Testing Done: * Run `certbot` with `-a certbot-route53:auth`, verify the plugin runs. * Run `certbot` with `--dns-route53`, verify the plugin runs.
2017-06-06 18:41:04 -04:00
name='certbot-dns-route53',
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
version=version,
route53: update setup.py to follow repo conventions (#4731) This change updates the setup script for the route53 plugin to more closely match conventions from other packages in the repository. Notable changes: * The version number is bumped to match the rest of Certbot. * The package now requires a matching version of ACME and core Certbot. * Contact information is updated. * Additional versions of Python are listed.
2017-05-26 17:44:05 -04:00
description="Route53 DNS Authenticator plugin for Certbot",
url='https://github.com/certbot/certbot',
author="Certbot Project",
author_email='client-dev@letsencrypt.org',
license='Apache License 2.0',
Finish dropping Python 2.6 and 3.3 support * Undo letsencrypt-auto changes * Remove ordereddict import * Add Python 3.4 tests to replace 3.3 * Add python_requires * update pipstrap
2018-02-16 19:20:45 -05:00
python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*',
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
classifiers=[
'Development Status :: 3 - Alpha',
'Environment :: Plugins',
'Intended Audience :: System Administrators',
'License :: OSI Approved :: Apache Software License',
'Operating System :: POSIX :: Linux',
'Programming Language :: Python',
'Programming Language :: Python :: 2',
'Programming Language :: Python :: 2.7',
route53: update setup.py to follow repo conventions (#4731) This change updates the setup script for the route53 plugin to more closely match conventions from other packages in the repository. Notable changes: * The version number is bumped to match the rest of Certbot. * The package now requires a matching version of ACME and core Certbot. * Contact information is updated. * Additional versions of Python are listed.
2017-05-26 17:44:05 -04:00
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5',
'Programming Language :: Python :: 3.6',
Advertise our packages work on Python 3.7. (#6183)
2018-07-09 12:17:03 -04:00
'Programming Language :: Python :: 3.7',
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
'Topic :: Internet :: WWW/HTTP',
'Topic :: Security',
'Topic :: System :: Installation/Setup',
'Topic :: System :: Networking',
'Topic :: System :: Systems Administration',
'Topic :: Utilities',
],
packages=find_packages(),
route53: update setup.py to follow repo conventions (#4731) This change updates the setup script for the route53 plugin to more closely match conventions from other packages in the repository. Notable changes: * The version number is bumped to match the rest of Certbot. * The package now requires a matching version of ACME and core Certbot. * Contact information is updated. * Additional versions of Python are listed.
2017-05-26 17:44:05 -04:00
include_package_data=True,
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
install_requires=install_requires,
Make it work as certbot-route53
2016-10-04 09:20:12 -04:00
keywords=['certbot', 'route53', 'aws'],
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
entry_points={
Make it work as certbot-route53
2016-10-04 09:20:12 -04:00
'certbot.plugins': [
route53: rename to match other DNS plugins (#4747) This change renames certbot-route53 to certbot-dns-route53 and updates the package's setup.py file to maintain backwards compatibility. Testing Done: * Run `certbot` with `-a certbot-route53:auth`, verify the plugin runs. * Run `certbot` with `--dns-route53`, verify the plugin runs.
2017-06-06 18:41:04 -04:00
'dns-route53 = certbot_dns_route53.dns_route53:Authenticator',
route53: avoid listing the plugin twice in the UI (#4794) Without this change, the Route53 plugin is listed twice when running Certbot interactively (once under the old name, once under the new name). This change ensures only the new name is shown, while maintaining hidden backwards compatibility with the old name.
2017-06-07 18:16:52 -04:00
'certbot-route53:auth = certbot_dns_route53.authenticator:Authenticator'
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
],
},
route53: rename to match other DNS plugins (#4747) This change renames certbot-route53 to certbot-dns-route53 and updates the package's setup.py file to maintain backwards compatibility. Testing Done: * Run `certbot` with `-a certbot-route53:auth`, verify the plugin runs. * Run `certbot` with `--dns-route53`, verify the plugin runs.
2017-06-06 18:41:04 -04:00
test_suite='certbot_dns_route53',
Initial commit, not safe to use
2016-02-01 01:33:17 -05:00
)
Reference in a new issue Copy permalink