ModusCreateOrg / ModusCreateOrg/devops-infra-demo
Split between packer / ansible and CodeDeploy phases for spin.py needs work
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 34
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that running packer and ansible left these files around (in the :
emperor.ini
src/infra-demo.ini
It looks like the split between the Ansible portion of the Python app deploy and the CodeDeploy portion is not quite right now. If we're going to use the WSGI Emperor, we should make sure it is installed in the base image, and then have the complete app, including the app-level WSGI file, get installed by the CodeDeploy package. Right now both configs are installed by Ansible / Packer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with spin.py and trace how Packer, Ansible, and CodeDeploy handle emperor.ini and src/infra-demo.ini. Check where the WSGI Emperor is installed and where the app-level WSGI file is packaged. Done means the base image contains the Emperor, while the CodeDeploy package installs the complete app and its app-level WSGI file without Ansible/Packer installing both configs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, aws, python
- Domain
- cloud, devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100