Merge branch 'master' into expect_one_of

Author: saravanan30erd

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: pending-review
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Runtime versions**
+Please run:
+
+```
+$ python --version
+$ chaos info core
+$ chaos info extensions
+```
+
+**To Reproduce**
+Steps to reproduce the behavior.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: pending-review
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/workflows/build.yaml

@@ -0,0 +1,42 @@
+name: Build
+
+on: [push, pull_request]
+
+jobs:
+  test:
+    runs-on: ubuntu-16.04
+    strategy:
+      matrix:
+        python-version: [3.6, 3.7, 3.8]
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v1
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip setuptools wheel
+        pip install -r requirements.txt -r requirements-dev.txt
+    - name: Checking the code syntax
+      run: |
+        pylama chaoslib
+    - name: Run tests
+      run: |
+        pip install -e .
+        pytest tests/
+
+  build:
+    runs-on: ubuntu-16.04
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v1
+      with:
+        python-version: '3.6'
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip setuptools wheel
+    - name: Build the choastoolkit-lib package
+      run : |
+        python3 setup.py build

.github/workflows/release.yaml

@@ -0,0 +1,37 @@
+name: Release
+
+on:
+  pull_request:
+    branches-ignore:
+      - 'master'
+  push:
+    tags:
+      - '[0-9]+.[0-9]+.[0-9]+'
+      - '[0-9]+.[0-9]+.[0-9]+rc[0-9]+'
+
+jobs:
+  release-to-pypi:
+    runs-on: ubuntu-16.04
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v1
+      with:
+        python-version: '3.6'
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install -U setuptools wheel twine
+    - name: Build and publish
+      env:
+        TWINE_USERNAME: chaostoolkit
+        TWINE_PASSWORD: ${{ secrets.PYPI_PWD }}
+      run: |
+        python3 setup.py release
+        twine upload dist/*
+    # push artifacts for other jobs to use
+    - name: Upload packages as artifacts
+      uses: actions/upload-artifact@v2-preview
+      with:
+        name: chaostoolkit-packages
+        path: dist/chaostoolkit-lib-*

.travis.yml

@@ -2,7 +2,129 @@
 
 ## [Unreleased][]
 
-[Unreleased]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.15.0...HEAD
+[Unreleased]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.19.0...HEAD
+
+## [1.19.0][] - 2021-02-16
+
+[1.19.0]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.18.3...1.19.0
+
+### Changed
+
+- Library now requires Python 3.6 [#208][ctk208]
+
+[ctk208]: https://github.com/chaostoolkit/chaostoolkit/issues/208
+
+## [1.18.3][] - 2021-02-16
+
+[1.18.3]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.18.2...1.18.3
+
+### Changed
+
+- Fix typo in `setup.cfg` from `install_require` to `install_requires`
+
+## [1.18.2][] - 2021-02-16
+
+[1.18.2]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.18.1...1.18.2
+
+### Changed
+
+- Fix release workflow by updating to latest setuptools
+
+## [1.18.1][] - 2021-02-16
+
+[1.18.1]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.18.0...1.18.1
+
+### Changed
+
+- Fix release package
+
+## [1.18.0][] - 2021-02-16
+
+[1.18.0]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.17.0...1.18.0
+
+### Changed
+
+- Moved from setup.py to declarative setup.cfg [#204][204]
+- Moved to pylama from pycodestyle [#205][205]
+
+[204]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/204
+[205]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/205
+
+## [1.17.0][] - 2021-02-15
+
+[1.17.0]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.16.0...1.17.0
+
+### Added
+
+- Activities can be requested not to be executed on a per activity basis, not
+  just as all or none. This can be used by a control to dynamically make
+  a decision on what to run.
+- Test that demonstrate how to wrap controls into decorators [#197][197]
+
+[197]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/197
+
+### Changed
+
+- Moved from TravisCI to GitHub Workflows [#201][201]
+
+[201]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/201
+
+## [1.16.0][] - 2020-12-02
+
+[1.16.0]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.15.1...1.16.0
+
+### Changed
+
+- Allow substitution to keep its original type when done in isolation.
+  [#180][180] [#195][195]. So let's assume we have the following configuration:
+
+  ```json
+  "configuration": {
+      "value": 8
+  }
+  ```
+
+  We can now use it as an argument of an action:
+
+  ```json
+  "provider": {
+      "arguments": {
+          "quantity": "${value}"
+      }
+  }
+  ```
+
+  Now, the `quantity` argument will indeed be an integer, when it was converted
+  to string until now. This works with any support Python objects, whether they
+  are scalars or nested.
+
+  If, you have something like this however
+
+
+  ```json
+  "provider": {
+      "arguments": {
+          "quantity": "I want ${value} apples"
+      }
+  }
+  ```
+
+  This will always remain a string.
+
+
+[180]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/180
+[195]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/195
+
+## [1.15.1][] - 2020-11-02
+
+[1.15.1]: https://github.com/chaostoolkit/chaostoolkit-lib/compare/1.15.0...1.15.1
+
+### Changed
+
+- Fixed a regression where the extra vars were not passed onto configuration
+  and secrets for overriding substitution [#192][192]
+
+[192]: https://github.com/chaostoolkit/chaostoolkit-lib/issues/192
 
 ### Added
 

CHANGELOG.md

@@ -0,0 +1,71 @@
+# Chaos Toolkit Code Of Conduct
+
+Chaos Toolkit adopts Debian project's Code Of Conduct for its
+participants and contributors.
+
+## Be respectful
+
+In the Chaos Toolkit project, inevitably there will be people with whom you
+may disagree, or find it difficult to cooperate. Accept that, but even
+so, remain respectful. Disagreement is no excuse for poor behaviour or
+personal attacks, and a community in which people feel threatened is
+not a healthy community.
+
+## Assume good faith
+
+Chaos Toolkit contributors have many ways of reaching our common goal
+of an open API for Chaos Engineering which may differ from your
+ways. Assume that other people are working towards this goal.
+
+Note that many of our Contributors are from around the globe, not
+native English speakers and may have different cultural backgrounds.
+
+## Be Collaborative
+
+Chaos Toolkit is a large project; there is always more to learn within
+it. It's good to ask for help when you need it. Similarly, offers for
+help should be seen in the context of our shared goal of improving
+Chaos Toolkit.
+
+When you make something for the benefit of the project, be willing to
+explain to others how it works, so that they can build on your work to
+make it even better.
+
+## Try to be concise
+
+Keep in mind that what you write once will be read by hundreds of
+people. Writing a short email means people can understand the
+conversation as efficiently as possible. When a long explanation is
+necessary, consider adding a summary.
+
+Try to bring new arguments to a conversation so that each mail adds
+something unique to the thread, keeping in mind that the rest of the
+thread still contains the other messages with arguments that have
+already been made.
+
+Try to stay on topic, especially in discussions that are already fairly large.
+
+## Be open
+
+Most ways of communication used within Chaos Toolkit allow for public
+and private communication. You should use public methods of
+communication for Chaos Toolkit related messages, unless posting
+something sensitive.
+
+## In case of problems
+
+While this code of conduct should be adhered to by participants, we
+recognize that sometimes people may have a bad day, or be unaware of
+some of the guidelines in this code of conduct. When that happens, you
+may reply to them and point out this code of conduct. Instances of
+otherwise unacceptable behavior may be reported by contacting team at
+contact@chaostoolkit.org. All complaints will be reviewed and
+investigated and will result in a response that is appropriate to the
+circumstances.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the [Debian Code Of Conduct][homepage], version 1.0
+
+[homepage]: https://www.debian.org/code_of_conduct

CODE_OF_CONDUCT.md

@@ -3,4 +3,3 @@ include requirements.txt
 include requirements-dev.txt
 include LICENSE
 include CHANGELOG.md
-include pytest.ini