include: - postgres - perforce.web-services.p4_project_services.deps p4_project_services db: postgres_database.present: - name: p4_project_services - user: postgres - db_user: postgres - owner: {{ pillar['postgres.user'] }} require: - sls: postgres # This is installed by our gem dependencies p4_project_services sequel migrate: cmd.run: - name: {{ pillar['p4_project_services.ruby.wrappers'] }}/bundle exec sequel -m ./migrations postgres://{{ pillar['postgres.user'] }}:{{ pillar['postgres.password'] }}@localhost:5432/p4_project_services - cwd: {{ pillar['p4_project_services.dir'] }} - user: webservices require: - sls: perforce.web-services.p4_project_services.deps - postgres_database: p4_project_services db
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#3 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#2 | 13530 | tjuricek |
Add p4_phoenix_services package and Salt configuration for deployment. This uncovered a couple of issues from the C++ API during it's conversion to C++03. So, in a nutshell, most operations, except for notifications, appear to be working (well, using Vagrant machines). |
||
#1 | 13515 | tjuricek |
Initial configuration for the p4_project_services. The tests haven't been run yet, so it's likely missing some more configuration. Using vagrant to even manage these environments may not be our realistic CD premise. I may end up moving some more responsibility into the Salt layer, which would make vSphere automation easier. |