Skip to content

Commit 9cf2d56

Browse files
authored
14.0.2+3.5.22 (#42)
* add .ansible to .gitignore * fix 'ansible-galaxy install role' -> 'ansible-galaxy role install' in README * update README/CHANGLOG
1 parent b6d4bbc commit 9cf2d56

File tree

4 files changed

+9
-4
lines changed

4 files changed

+9
-4
lines changed

.ansible/roles/githubixx.etcd

Lines changed: 0 additions & 1 deletion
This file was deleted.

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,3 @@
11
*.swp
22
*.retry
3+
.ansible

CHANGELOG.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
# Changelog
22

3+
## 14.0.2+3.5.22
4+
5+
- add `.ansible` directory to `.gitignore`
6+
- fix `ansible-galaxy install role` -> `ansible-galaxy role install` in README
7+
38
## 14.0.1+3.5.22
49

510
- fix `README.md`

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Upgrading a etcd cluster which was installed by this role is described in [here]
99

1010
## Versions
1111

12-
I tag every release and try to stay with [semantic versioning](http://semver.org). If you want to use the role I recommend to checkout the latest tag. The master branch is basically development while the tags mark stable releases. But in general I try to keep master in good shape too. A tag `14.0.1+3.5.22` means this is release `14.0.1` of this role and it's meant to be used with etcd version `3.5.22` (but should work with newer versions also). If the role itself changes `X.Y.Z` before `+` will increase. If the etcd version changes `X.Y.Z` after `+` will increase. This allows to tag bugfixes and new major versions of the role while it's still developed for a specific etcd release.
12+
I tag every release and try to stay with [semantic versioning](http://semver.org). If you want to use the role I recommend to checkout the latest tag. The master branch is basically development while the tags mark stable releases. But in general I try to keep master in good shape too. A tag `14.0.2+3.5.22` means this is release `14.0.2` of this role and it's meant to be used with etcd version `3.5.22` (but should work with newer versions also). If the role itself changes `X.Y.Z` before `+` will increase. If the etcd version changes `X.Y.Z` after `+` will increase. This allows to tag bugfixes and new major versions of the role while it's still developed for a specific etcd release.
1313

1414
## Changelog
1515

@@ -25,7 +25,7 @@ This role requires that you already created some certificates for `etcd` (see [K
2525
`git clone https://github.com/githubixx/ansible-role-etcd.git githubixx.etcd`
2626

2727
- Via `ansible-galaxy` command and download directly from Ansible Galaxy:
28-
`ansible-galaxy install role githubixx.etcd`
28+
`ansible-galaxy role install githubixx.etcd`
2929

3030
- Create a `requirements.yml` file with the following content (this will download the role from Github) and install with
3131
`ansible-galaxy role install -r requirements.yml` (change `version` if needed):
@@ -35,7 +35,7 @@ This role requires that you already created some certificates for `etcd` (see [K
3535
roles:
3636
- name: githubixx.etcd
3737
src: https://github.com/githubixx/ansible-role-etcd.git
38-
version: 14.0.1+3.5.22
38+
version: 14.0.2+3.5.22
3939
```
4040
4141
## Role Variables

0 commit comments

Comments
 (0)