Say my team is developing a Health Connect production. We're using Embedded Git for source control, with each developer working on a private namespace on the same instance. The production includes some inbound services that have a port number.
Some options are:
- use a shared set of system default settings defining the port number: then there are errors because services in different namespaces try to claim the same port number
- leave the port numbers null: the production fails to start because of services missing port numbers
- leave the port numbers null, and disable all the services except the ones you're currently working on: the "enabled" flag gets exported to source control, and incorrectly ends up deployed
- leave the port numbers null, and use System Default Settings to disable all the services except the ones you're currently working on: it's a huge pain to manage all these system default settings and change them manually every time you switch branch to work on a different feature.
Let's brainstorm a better way to do this. Potentially a new feature in Embedded Git, or maybe there's a better way to handle this using existing product features.
Say my team is developing a Health Connect production. We're using Embedded Git for source control, with each developer working on a private namespace on the same instance. The production includes some inbound services that have a port number.
Some options are:
Let's brainstorm a better way to do this. Potentially a new feature in Embedded Git, or maybe there's a better way to handle this using existing product features.