upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-06-15 11:39:12 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
certbot/tools/venv3.sh

28 lines
651 B
Bash
Raw Permalink Normal View History

Developer virtualenv bootstrap scripts.
2015-09-27 16:57:31 -04:00
#!/bin/sh -xe
Rename misc files
2016-04-14 13:20:23 -04:00
# Developer Python3 virtualenv setup for Certbot
Developer virtualenv bootstrap scripts.
2015-09-27 16:57:31 -04:00
Extend tools/venv3.sh to support full certbot development (#4532)
2017-04-20 12:09:20 -04:00
if command -v python3; then
export VENV_NAME="${VENV_NAME:-venv3}"
export VENV_ARGS="--python python3"
else
echo "Couldn't find python3 in $PATH"
exit 1
fi
Developer virtualenv bootstrap scripts.
2015-09-27 16:57:31 -04:00
Fix broken reference to script in old bootstrap directory
2016-02-10 19:38:24 -05:00
./tools/_venv_common.sh \
Clean up dev/testing extras messup (fixes #2140).
2016-01-10 13:37:41 -05:00
-e acme[dev] \
Extend tools/venv3.sh to support full certbot development (#4532)
2017-04-20 12:09:20 -04:00
-e .[dev,docs] \
-e certbot-apache \
Cloudflare DNS Authenticator Implement an Authenticator which can fulfill a dns-01 challenge using the Cloudflare API. Applicable only for domains using Cloudflare for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-cloudflare -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-cloudflare -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting cloudflare interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Credentials file missing e-mail address. * Credentials file with blank API key. * Credentials file with incorrect e-mail address. * Credentials file with malformed API key. * Credentials file with invalid API key. * Domain name not registered to Cloudflare account.
2017-05-02 13:12:23 -04:00
-e certbot-dns-cloudflare \
CloudXNS DNS Authenticator (#4585) Implement an Authenticator which can fulfill a dns-01 challenge using the CloudXNS DNS API. Applicable only for domains using CloudXNS DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-cloudxns -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-cloudxns -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting cloudxns interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Domain name not registered to CloudXNS account.
2017-05-19 19:23:53 -04:00
-e certbot-dns-cloudxns \
DigitalOcean DNS Authenticator Implement an Authenticator which can fulfill a dns-01 challenge using the DigitalOcean API. Applicable only for domains using DigitalOcean for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-digitalocean -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-digitalocean -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting digitalocean interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Credentials file missing token. * Credentials file with blank token. * Credentials file with incorrect token. * Domain name not registered to DigitalOcean account.
2017-04-28 17:53:07 -04:00
-e certbot-dns-digitalocean \
DNSimple DNS Authenticator (#4587) Implement an Authenticator which can fulfill a dns-01 challenge using the DNSimple DNS API. Applicable only for domains using DNSimple DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-dnsimple -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-dnsimple -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting dnsimple interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file with an invalid token. * Path to credentials file without a token. * Domain name not registered to DNSimple account.
2017-05-22 20:06:04 -04:00
-e certbot-dns-dnsimple \
DNS Made Easy DNS Authenticator (#4603) Implement an Authenticator which can fulfill a dns-01 challenge using the DNS Made Easy API. Applicable only for domains using DNS Made Easy. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: (`http://api.sandbox.dnsmadeeasy.com/V2.0` used as the `api_endpoint` for all manual testing) * Used `certbot certonly --dns-dnsmadeeasy -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file with an invalid API key. * Path to credentials file with a malformed API key. * Path to credentials file with an invalid Secret key. * Path to credentials file with a malformed Secret key. * Domain name not registered to DNS Made Easy account.
2017-06-15 19:41:00 -04:00
-e certbot-dns-dnsmadeeasy \
Google Cloud DNS Authenticator (#4581) Implement an Authenticator which can fulfill a dns-01 challenge using the Google Cloud DNS API. Applicable only for domains using Google Cloud DNS for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-google -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-google -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting google interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Domain name not registered to Google Cloud Platform account.
2017-05-17 14:26:26 -04:00
-e certbot-dns-google \
LuaDNS DNS Authenticator (#4605) Implement an Authenticator which can fulfill a dns-01 challenge using the LuaDNS API. Applicable only for domains using LuaDNS for DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-luadns -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file without an email. * Path to credentials file with an invalid email. * Path to credentials file without a token. * Path to credentials file with an invalid token. * Domain name not registered to LuaDNS account.
2017-06-16 17:43:12 -04:00
-e certbot-dns-luadns \
NS1 DNS Authenticator (#4602) Implement an Authenticator which can fulfill a dns-01 challenge using the NS1 DNS API. Applicable only for domains using NS1 DNS. Testing Done: * `tox -e py27` * `tox -e lint` * Manual testing: * Used `certbot certonly --dns-nsone -d`, specifying a credentials file as a command line argument. Verified that a certificate was successfully obtained without user interaction. * Used `certbot certonly --dns-nsone -d`, without specifying a credentials file as a command line argument. Verified that the user was prompted and that a certificate was successfully obtained. * Used `certbot certonly -d`. Verified that the user was prompted for a credentials file after selecting dnsimple interactively and that a certificate was successfully obtained. * Used `certbot renew --force-renewal`. Verified that certificates were renewed without user interaction. * Negative testing: * Path to non-existent credentials file. * Credentials file with unsafe permissions (644). * Path to credentials file with an invalid token. * Path to credentials file without a token. * Domain name not registered to NS1 account.
2017-05-26 14:24:38 -04:00
-e certbot-dns-nsone \
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
-e certbot-dns-route53 \
Extend tools/venv3.sh to support full certbot development (#4532)
2017-04-20 12:09:20 -04:00
-e certbot-nginx \
-e letshelp-certbot \
-e certbot-compatibility-test
Reference in a new issue Copy permalink