Pulp

If the environment variable is not set, it will still default to /etc/pulp/server.yaml right? I think most production installations will want it set there.

Does the devel playbook already install the server.yaml file? If so where?

@asmacdo says the devel environment installs it already to /etc/pulp/server.yaml with this

I was thinking that an environmental variable should be required, rather than us checking to see if the envvar exists and defaulting to a /etc/pulp/server.yaml that might not exist.

The majority of installations will have it installed at /etc/pulp/server.yaml. All rpm based installs for example will have it set there. We should really default to /etc/pulp/server.yaml.

To implement I was thinking we don't even have to check the filesystem at all. We could:

if env_var_for_conf_is_set:
  path_to_conf = the_env_set_path
else:
  path_to_conf = '/etc/pulp/server.yaml'

We can handle the default as a separate story also and for now require the environment variable. If we do add a default I want it to be something that is very cross-platform.

Containerized deployments will mostly use the environment variable, so that's a solid production use case.

I'm still happy with defaulting to /etc/pulp/server.yaml though.

We decided to not set a default for now and to rely on the environment variable in 100% of cases. We can set a default as followup work if we even want to.