Releases: kabirbaidhya/boss
Releases · kabirbaidhya/boss
v1.0.3
v1.0.3-test.1
Bump version 1.0.3-test.1
v1.0.3-alpha.1
Bump version 1.0.3-alpha.1
v1.0.2
v1.0.1
Improvements
- Upgrade core dependencies - paramiko, cryptography, fabric and pyyaml #157 [internals] (@kabirbaidhya)
- Use setuptools for development and remove requirements-dev.txt #156 (@kabirbaidhya)
- Display
README.md
correctly on pypi repository - https://pypi.org/project/boss-cli/ #155 (@kabirbaidhya)
v1.0.0
Boss v1.0.0 - first stable release
The first stable release v1.0.0
after all the previous alpha and beta releases 🎉 🎆 🙌 😅.
No additional changes introduced after v1.0.0-beta.6.
Check the releases and change log to know about the changes in detail.
$ pip install boss-cli==1.0.0
v1.0.0-beta.6
Bug Fixes
- When vault server is not reachable - boss throws
Error loading config file "boss.yml"
error #149 [bug] - Resolve deprecation errors due to paramiko's cryptography dependency version and the cwd issue on run() function #154 [bug] (@kabirbaidhya)
Improvements
- Use yaml.FullLoader for loading yaml config #153 [security] (@kabirbaidhya)
- Fix vulnerability CVE-2017-18342 - upgrade dependency pyyaml #152 (@kabirbaidhya)
v1.0.0-beta.5
Bug Fixes
- Display specific vault error messages if boss halts due to vault error #150 [bug] [config] (@kabirbaidhya)
v1.0.0-beta.4
Improvements
- Remote source deployment now uses
deployment.base_dir
instead ofapp_dir
, making config consistent across all the deployment presets #148 [breaking-change] [deployment] [remote-source] (@kabirbaidhya)- Previously the
app_dir
was being used as a current working directory setter on the remote which being used by default in the remote-source deployment as the app root directory. Now, all the presets includingremote-source
uses thedeployment.base_dir
as the application base directory - For a setting a default current directory for general remote execution a new config option
cwd
is introduced. But this will be overridden bybase_dir
in all the deployment workflows.
- Previously the
Breaking Changes
- Config option
app_dir
has been removed,deployment.base_dir
is the only option now. - The
build
andsync
aren't exposed as cli executable commands anymore.
Closed issues
- Use the local branch name by default on remote-source deployment too #144 [deployment] [remote-source]
v1.0.0-beta.3
Improvements
- Support using local ref (by default) for remote-source deployment #145 [breaking-change] [deployment] [feature] [remote-source] (@kabirbaidhya)
- Introduce
deployment.use_local_ref
config option. When this istrue
theremote-source
deployment now uses the local branch / commit to deploy to remote instead of the configured stage's default branch. - If this is
false
then the default behavior would proceed i.e uses stage config's default branch.
- Introduce
Breaking Changes
-
Default behavior of
remote-source
deployment changed
Default value of this newly introduced flagdeployment.use_local_ref
has been settrue
.This changes the default behavior of
fab <stage> deploy
command. Now instead of deploying the stage's default branch this will use the local branch or commit instead for deployment.However
fab <stage> deploy:<branch>
is still possible and is still do the previous behavior i.e to deploy specific branch as provided.
Fixed bugs
- Fix issue with deploying with a specific commit on remote-source deployment preset #146 [bug] [remote-source] (@kabirbaidhya)