Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Letsencrypt auto release #2

Merged

Conversation

pde
Copy link

@pde pde commented Jan 11, 2016

Various updates including some client integration with the new leauto.

 - move them to the top for clarity
 - accept them in any position
 - shadow & document them in the Python client
elif [ "$arg" = "--no-self-upgrade" ] ; then
# Do not upgrade this script (also prevents client upgrades, because each
# copy of the script pins a hash of the python client)
NO_SELF_UPGRADE=1
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, this means the client has to be aware of all le-auto flags, though they do nothing there. If we could come up with a plain-Bourne way of slicing the le-auto args out of the arg list, we wouldn't have to do that. Any ideas? Bourne supports only the single array, $@, and has no slicing ops.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose we could have a Python script do the slicing, but that's even more complicated. Let's keep this for now.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On the plus side, if the python code knows about these flags, then it can also provide documentation for them.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is true. Wrapper scripts that want to have their own flags are tricky, as I learned with peep.

@erikrose erikrose force-pushed the letsencrypt-auto-release branch 5 times, most recently from bcdf0c5 to ed56264 Compare January 12, 2016 15:46
@erikrose
Copy link
Owner

I tried the merge but found that it failed one of the tox -e le_auto tests:

======================================================================
ERROR: Exercise most branches of letsencrypt-auto.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/lea/letsencrypt/letsencrypt-auto-source/tests/auto_test.py", line 294, in test_successes
    err.strip().splitlines()[-1]))
IndexError: list index out of range

In other words, it doesn't seem to install a letsencrypt script that prints its version when passed --version.

@erikrose erikrose force-pushed the letsencrypt-auto-release branch 2 times, most recently from 1899f8e to 7ee23b7 Compare January 12, 2016 18:34
@erikrose erikrose merged commit c8c4976 into erikrose:letsencrypt-auto-release Jan 13, 2016
erikrose added a commit that referenced this pull request Jan 13, 2016
…ove le-auto's option parsing.

If the new le-auto tests well in the minutes or hours after release, we'll make another commit to master that removes the old le-auto stuff.

Close #2.
erikrose added a commit that referenced this pull request Jan 13, 2016
…ove le-auto's option parsing.

If the new le-auto works well in the minutes or hours after release, we'll make another commit to master that removes the old le-auto and bootstrap scripts.

Close #2.
@erikrose
Copy link
Owner

Rolled back and re-merged in d813097.

erikrose pushed a commit that referenced this pull request Jun 9, 2017
Make certbot-route53 python3 compatible
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants