René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[FEATURE] Automated testing, build and deployment to PyPi","articleBody":"**Feature Description**\r\n\r\nCurrently CI/CD covers the web site deployment only, need to expand this to cover package updates (any changes to `stackql-deploy/**`)\r\n  .  If changes are made to files in this dir tree, then:\r\n\r\n1. test that the package version (semver) has been updated (from the previous `main` version (`setup.py` and `__init__.py`)\r\n2. run some basic automated tests (deploying and tearing down basic stacks to AWS, Azure and Google) - provider creds supplied as actions secrets - this can include testing of the [marketplace GitHub Action](https://github.com/marketplace/actions/stackql-deploy)\r\n3. build and publish to PyPi automatically upon merge to `main`\r\n\r\nsteps for __3__ are:\r\n\r\n```bash\r\npip install --upgrade build\r\npip install twine\r\npython3 -m build\r\ntwine upload --config-file .pypirc dist/*\r\n```\r\n\r\n`.pypirc` contains the access token for PyPi, so this would need to be written in an actions step from an actions secret\r\n\r\n","author":{"url":"https://github.com/jeffreyaven","@type":"Person","name":"jeffreyaven"},"datePublished":"2024-10-09T21:27:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/46/stackql-deploy/issues/46"}