Chris Johnson
Chris Johnson
> Hello @jiacheng-0 , > > It actually exists this -> https://github.com/duo-labs/cloudmapper#using-a-docker-container > > Have you checked it out? > > Cheers! The container doesn't build... so far here's the...
> Has already been fixed in other PRs, yet not merged. Yes, that's 1 of 2 things I had to fix to get the container to build.
Workaround: Install setuptools 57.x.x For example: ``` pip install --upgrade pip setuptools==57.5.0 pip install --upgrade python-pushover pip freeze > requirements.txt ```
Understood and agreed... given the last release on this repo was in 2018, I figured others might land here and find the workaround helpful.
I've encountered this as well, i started creating v0.0.0 releases every time i create a new repo
So, this action already assumed the prior tag to be `0.0.0` when there is no tag in the repo. I have a no-code fix for this that I've implemented on...
I've a setup which does RC versioning for all branches except `main`, what I'm doing differently is using a dynamic `append_to_pre_release_tag` which appends the github run id. However, mine also...
Please do submit a PR
i like some of the concepts here, however i think this is too large of a PR. IMO it should be broken into parts like: translation refactoring, execution logging, etc....
+1 This would also fix the improper use of Prometheus as a deployment. Prometheus needs to be a stateful set due to it's pvc.