What is the vault application life cycle?

We don't have a specific page, although it sounds like something we could create.  Some of those methods actually call each other (e.g. Unitialize calls UninitializeApplication).

Do you have any specific issue that caused this query?

We don't have a specific page, although it sounds like something we could create.  Some of those methods actually call each other (e.g. Unitialize calls UninitializeApplication).

Do you have any specific issue that caused this query?

Hi Craig.

We want to log suff using AddCustomEventEntry as well as access the values in the Configuratton object after they're loaded and don't know when it's safe to do each one.

Hi I think I can access the config in IniailizeApplicaton and I can access the vault in StartApplication

I overrode most of the methods and this seems to be the order of events. ctor is the VaultApplication constructor.

INSTALL

1. ctor
2. Install
3. Install => InstallApplication

RESTART

4. ctor
5. Intialize(Vault)
6. Intialize(Vault) => UninitializeImpl(Value)
7. Intialize(Vault) => PopulateConfigurationObjects(Value)
8. Intialize(Vault) => PopulateConfigurationObjectsAndValidate(Value)
9. Intialize(Vault) => PopulateConfigurationObjectsAndValidate(Value) => ValidateMetadataStructure(Vault)
10. Intialize(Vault) => InitializeImpl(Vault)
11. Intialize(Vault) => InitializeApplication(Vault)
12. Run(ScriptEnvironment) => AssertApplicationInStableState(EnvironmentBase)
13. StartOperations(Vault)
14. StartOperations(Vault) => InitializeAvailabilityGroupStatusWriter(Vault)
15. StartOperations(Vault) => StartApplication()

UNINSTALL

1. ctor
2. Uninstall(Vault)
3. Uninstall(Vault) => UninstallApplication(Vault)