Feel free to open pull requests with additional features or improvements!
Integration tests will automatically start a Vault server in the background. Just make sure
vault binary is available in your
This project uses pip-tool’s
pip-compile utility to manage its various requirements.
Any given requirements file can be manually updated by following the pip-compile comments at the top of the file. Alternatively, the
update-all-requirements Makefile target can be used to update requirements across the board (this has a dependency on docker being available).
Example code or general guides for methods in this module can be added under docs/usage. Any newly added or updated method in this module will ideally have a corresponding addition to these examples. New usage sections should also be added to the table of contents tracked in docs/usage.rst.
Backwards Compatibility Breaking Changes¶
Due to the close connection between this module and HashiCorp Vault versions, breaking changes are sometimes required. This can also occur as part of code refactoring to enable improvements in the module generally. In these cases:
- A deprecation notice should be displayed to callers of the module until the minor revision +2. E.g., a notice added in version 0.6.2 could see the marked method / functionality removed in version 0.8.0.
- Breaking changes should be called out in the CHANGELOG.md for the affected version.
Package Publishing Checklist¶
The follow list uses version number
0.6.2, this string should be updated to match the intended release version. It is based on this document: https://gist.github.com/audreyr/5990987
[ ] Ensure your working directory is clear by running: .. code-block:: guess
[ ] Checkout the
developbranch: .. code-block:: guess
git checkout develop git pull
[ ] Update CHANGELOG.md with a list of the included changes. Those changes can be reviewed, and their associated GitHub PR number confirmed, via GitHub’s pull request diff. E.g.: https://github.com/hvac/hvac/compare/master…develop. Then commit the changes: .. code-block:: guess
git commit CHANGELOG.md -m ‘Changelog updates for vX.X.X release’
[ ] Update version number using bumpversion. Releases typically just use the “patch” bumpversion option; but “minor” and “major” are available as needed as needed. This will also add an appropriate git commit and tag for the new version. .. code-block:: guess
[ ] Install the package again for local development, but with the new version number: .. code-block:: guess
python setup.py develop
[ ] Run the tests and verify that they all pass: .. code-block:: guess
[ ] Invoke setup.py / setuptools via the “package” Makefile job to create the release version’s sdist and wheel artifacts:
twine upload --repository-url https://test.pypi.org/legacy/ dist/*.tar.gz dist/*.whl
[ ] Check the TestPyPI project page to make sure that the README, and release notes display properly: https://test.pypi.org/project/hvac/
[ ] Test that the version is correctly listed and it pip installs (
mktmpenvis available via the virtualenvwrapper module) using the TestPyPI repository (Note: installation will currently fail due to missing recent releases of
requestson TestPyPI): .. code-block:: guess
[ ] Upload the sdist and whl files to the draft GitHub release as attached “binaries”.
[ ] Git push the updated develop branch (
git push) and open a PR to merge the develop branch into master: https://github.com/hvac/hvac/compare/master…develop
twine upload dist/*.tar.gz dist/*.whl
[ ] Check the PyPI project page to make sure that the README, and release notes display properly: https://pypi.org/project/hvac/
mktmpenv pip install --no-cache-dir hvac== <verify releaes version shows up with the correct formatting in the resulting list> pip install --no-cache-dir hvac==0.6.2 <verify hvac functionality> deactivate
[ ] Publish the draft release on GitHub: https://github.com/hvac/hvac/releases