potiuk commented on PR #24588: URL: https://github.com/apache/airflow/pull/24588#issuecomment-1511700537
See: https://github.com/apache/airflow/blob/main/TESTING.rst#helm-unit-tests Those tests are simply executing a "helm" that you see there and you can reproduce what they do by runnig te command with some values generated dynamically - generate the same values (they got generated in /tmp/* file by the test) and convert the command parameter in the shell command if you want to reproduce what they do manually (make sure you run it in the same working directory the orignal command does.. The command will be something like: "helm template release-name. ..." based on: ``` 'helm', 'template', 'release-name', '/opt/airflow/chart', '--values', '/tmp/tmpjppcs087', '--kube-version', '1.23.13', '--namespace', 'default', '--show-only', 'templates/scheduler/scheduler-deployment.yaml', '--show-only', 'templates/workers/worker-deployment.yaml', '--show-only', 'templates/webserver/webserver-deployment.yaml ``` You can also run those tests from IDE via remote debugging or SSH debugging (described in CONTRIBUTING docs - including with screenshots - you can even pause breakpoint just before the command to inspect the environment and generated values file. Or you can just install helm and run the tests locally - they should run if you have `helm` command line installed on your system (likely you need a POSIX system if you try to run it on Windows, it's not guaranteed to work on Windows). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
