py-pve-cloud 0.2.0__tar.gz → 0.2.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.

This version of py-pve-cloud might be problematic. Click here for more details.

Files changed (24) hide show
  1. {py_pve_cloud-0.2.0/src/py_pve_cloud.egg-info → py_pve_cloud-0.2.2}/PKG-INFO +1 -1
  2. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/README.md +17 -2
  3. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/pyproject.toml +1 -1
  4. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2/src/py_pve_cloud.egg-info}/PKG-INFO +1 -1
  5. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/LICENSE +0 -0
  6. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/setup.cfg +0 -0
  7. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/cli/pvcli.py +0 -0
  8. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/cli/pvclu.py +0 -0
  9. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/lib/inventory.py +0 -0
  10. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/alchemy.py +0 -0
  11. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/alembic.ini +0 -0
  12. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/env.py +0 -0
  13. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/24a548bfce3e_len_rules_enforcements.py +0 -0
  14. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/27724e407e2b_proxy_fqdn.py +0 -0
  15. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/3c95509a5de9_fix.py +0 -0
  16. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/7868bcd05006_migrate_old.py +0 -0
  17. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/7dea8c4ee39f_init.py +0 -0
  18. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/944a8fd5d5bc_ext_ctrl_plns.py +0 -0
  19. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/pve_cloud/orm/migrations/versions/d9b711555be8_ext_control_plane.py +0 -0
  20. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/py_pve_cloud.egg-info/SOURCES.txt +0 -0
  21. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/py_pve_cloud.egg-info/dependency_links.txt +0 -0
  22. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/py_pve_cloud.egg-info/entry_points.txt +0 -0
  23. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/py_pve_cloud.egg-info/requires.txt +0 -0
  24. {py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/src/py_pve_cloud.egg-info/top_level.txt +0 -0
{py_pve_cloud-0.2.0/src/py_pve_cloud.egg-info → py_pve_cloud-0.2.2}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: py-pve-cloud
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Author-email: Tobias Huebner <tobias.huebner@vmzberlin.com>
5
5
  License-Expression: GPL-3.0-or-later
6
6
  License-File: LICENSE
{py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/README.md RENAMED
@@ -10,12 +10,27 @@ edit `src/orm/alchemy.py` database classes and run `alembic revision --auto-ener
10
10
 
11
11
  you also need to `export PG_CONN_STR=postgresql+psycopg2://postgres:{{ patroni_postgres_pw }}@{{ proxy or master ip }}:{{ 5000 / 5432 }}/pve_cloud?sslmode=disable` env variable first with a testing database for alembic to work against. to create a new migration the database needs to be on the latest version, run `alembic upgrade head` to upgrade it.
12
12
 
13
+ ## Releasing to pypi manually
13
14
 
14
- ## Releasing to pypi
15
+ increment the version in pyproject.toml and run `pip install build==1.3.0 twine==6.2.0` and this to release:
15
16
 
16
17
  ```bash
17
- pip install build twine
18
+ export PYPI_TOKEN= # set pve cloud pypi account access token
19
+
18
20
  rm -rf dist
19
21
  python3 -m build
20
22
  python3 -m twine upload dist/*
21
23
  ```
24
+
25
+ ## Releasing via pipeline
26
+
27
+ add `*.*.*` as protected tag pattern under Repository settings in gitlab.
28
+
29
+ set the PYPI_TOKEN variable as a ci/cd variable.
30
+
31
+ increment the version in pyproject.toml, commit and tag the commit with the same semver version.
32
+
33
+
34
+ ## Developing locally
35
+
36
+ activate your venv and simply run `pip install -e .` to install this package in edit mode. Any changes will be live.
{py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "py-pve-cloud"
7
- version = "0.2.0"
7
+ version = "0.2.2"
8
8
  authors = [{ name = "Tobias Huebner", email = "tobias.huebner@vmzberlin.com" }]
9
9
  license = "GPL-3.0-or-later"
10
10
  license-files = ["LICENSE"]
{py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2/src/py_pve_cloud.egg-info}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: py-pve-cloud
3
- Version: 0.2.0
3
+ Version: 0.2.2
4
4
  Author-email: Tobias Huebner <tobias.huebner@vmzberlin.com>
5
5
  License-Expression: GPL-3.0-or-later
6
6
  License-File: LICENSE
{py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/LICENSE RENAMED
File without changes
{py_pve_cloud-0.2.0 → py_pve_cloud-0.2.2}/setup.cfg RENAMED
File without changes