I would have thought the definition in the vars file would be sufficient. How are you running the ansible script? Is it possible that it's not pointing at the right environment?
It looks like you have invalid directory structure. Perhaps by a mistake you might have copied the example configuration directory to inventories/myproject/example instead of inventories/myproject. If you move all the files in example directory to inventories/myproject, delete the examples subdirectory and run the commands, it should work.
Please review the documentation which states below command
Thanks for pointing that out, however it looks like the docs have been updated from the time i was initially trying to deploy the commcare-sync to date.
When i tried running the script after moving the file locations it found the correct configuration file and was able to proceed with the deployment however i was then presented with this error:
fatal: [local1]: FAILED! => {"changed": true, "cmd": "/home/ansible/www/.virtualenvs/superset/bin/superset db upgrade", "delta": "0:00:01.394522", "end": "2022-08-11 13:03:19.545219", "msg": "non-zero return code", "rc": 1, "start": "2022-08-11 13:03:18.150697", "stderr": "--------------------------------------------------------------------------------\n WARNING\n--------------------------------------------------------------------------------\nA Default SECRET_KEY was detected, please use superset_config.py to override it.\nUse a strong complex alphanumeric string and use a tool to help you generate \na sufficiently random sequence, ex: openssl rand -base64 42\n--------------------------------------------------------------------------------\n--------------------------------------------------------------------------------\nlogging was configured successfully\n2022-08-11 13:03:19,134:INFO:superset.utils.logging_configurator:logging was configured successfully\n2022-08-11 13:03:19,138:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>\nFalling back to the built-in cache, that stores data in the metadata database, for the following cache: FILTER_STATE_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments\n2022-08-11 13:03:19,139:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: FILTER_STATE_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments\nFalling back to the built-in cache, that stores data in the metadata database, for the following cache: EXPLORE_FORM_DATA_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments\n2022-08-11 13:03:19,141:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: EXPLORE_FORM_DATA_CACHE_CONFIG. It is recommended to use RedisCache, MemcachedCache or another dedicated caching backend for production deployments\nFailed to create app\nTraceback (