Skip to content

Commit 4b35baa

Browse files
committed
Add README.md
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
1 parent c49b624 commit 4b35baa

1 file changed

Lines changed: 33 additions & 0 deletions

File tree

README.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Operator Manifest
2+
3+
A python library for processing operator manifests.
4+
5+
## Running the Unit Tests
6+
7+
The testing environment is managed by [tox](https://tox.readthedocs.io/en/latest/). Simply run
8+
`tox` and all the linting and unit tests will run.
9+
10+
If you'd like to run a specific unit test, you can do the following:
11+
12+
```bash
13+
tox -e py37 tests/test_operator.py::TestOperatorCSV::test_valuefrom_references_not_allowed
14+
```
15+
16+
## Dependency Management
17+
18+
To manage dependencies, this project uses [pip-tools](https://github.com/jazzband/pip-tools) so that
19+
the production dependencies are pinned and the hashes of the dependencies are verified during
20+
installation.
21+
22+
The unpinned dependencies are recorded in `setup.py`, and to generate the `requirements.txt` file,
23+
run `pip-compile --generate-hashes --output-file=requirements.txt`. This is only necessary when
24+
adding a new package. To upgrade a package, use the `-P` argument of the `pip-compile` command.
25+
26+
To update `requirements-test.txt`, run
27+
`pip-compile --generate-hashes requirements-test.in -o requirements-test.txt`.
28+
29+
When installing the dependencies in a production environment, run
30+
`pip install --require-hashes -r requirements.txt`. Alternatively, you may use
31+
`pip-sync requirements.txt`, which will make sure your virtualenv only has the packages listed in
32+
`requirements.txt`.
33+

0 commit comments

Comments
 (0)