User story #9011
closed
Automatically call rudder-init on postinstall
Added by Benoît PECCATTE about 8 years ago.
Updated almost 4 years ago.
Description
The idea here is to be able to have a fully automated, non-interactive post-install.
It implies that by default, a new Rudder installation will have all the known network of the machine added in allowed networks.
We need to update the documentation on installation, with a new step "reviewing networks access".
This is possible because we added the network detection in linked ticket (#9010)
We also must provide a way to give the authorized networks to automate rudder install (either by API, or by looking for the existence of a specific env variable and use it in place of auto, or with a dedicated command).
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
- Target version changed from 4.0.0~rc2 to 4.1.0~beta1
I'd not suggest to automatically call rudder-init in the post-install phase. My thinking is, if you'd want to create a docker container hosting Rudder, you'd "init" the environment during the "container build" Phase, before the final instance of the container is created. What if that environment has a different environment?
Additionally, you would not want to init rudder in a building environment, since this would mean init'ing LDAP/DB with values that would vanish when those services would start in the final environment, that might have pgsql and ldap's datadir mapped to an external directory...
- Target version changed from 4.1.0~beta1 to 4.1.0~beta2
- Target version changed from 4.1.0~beta2 to 4.1.0~beta3
- Target version changed from 4.1.0~beta3 to 4.1.0~rc1
- Target version changed from 4.1.0~rc1 to 4.2.0~beta1
- Target version changed from 4.2.0~beta1 to 4.2.0~beta2
- Target version changed from 4.2.0~beta2 to 4.2.0~beta3
- Target version changed from 4.2.0~beta3 to 4.2.0~rc1
- Target version changed from 4.2.0~rc1 to 4.2.0~rc2
- Target version changed from 4.2.0~rc2 to 4.2.0
- Target version changed from 4.2.0 to 4.2.1
- Target version changed from 4.2.1 to 4.2.2
- Target version changed from 4.2.2 to 4.2.3
- Target version changed from 4.2.3 to 4.2.4
- Target version changed from 4.2.4 to Ideas (not version specific)
- Status changed from New to Rejected
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by