diff options
| author | Håkon Hallingstad <hakon@verizonmedia.com> | 2020-02-23 18:11:44 +0100 |
|---|---|---|
| committer | Håkon Hallingstad <hakon@verizonmedia.com> | 2020-02-23 18:11:44 +0100 |
| commit | 988131792a9bf0cd22072622ec3ffd2d62efa62d (patch) | |
| tree | 4e2f0e4a2c6638cc12a4ac3d3145f85bb745bebc /config-provisioning/abi-spec.json | |
| parent | 465e0e5ab20337d9f8023cb0371c57927be06ff6 (diff) | |
Define completeness of SuperModel and DuperModel
In order for Orchestrator to remove application data from ZooKeeper, it must
know which applications do NOT exist. Since the duper model starts with 0
applications, always, the only way of knowing what applications do not exist is
for the bootstrap code to notify the super model/duper model when bootstrap is
complete. There are 2 sources of applications that must signal completeness:
- The super model, once all applications have been redeployed in
ConfigServerBootstrap.
- The infrastructure application, in the InfrastructureProvisioner the first
time it runs.
Diffstat (limited to 'config-provisioning/abi-spec.json')
| -rw-r--r-- | config-provisioning/abi-spec.json | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/config-provisioning/abi-spec.json b/config-provisioning/abi-spec.json index 45f8171436d..c37e3693457 100644 --- a/config-provisioning/abi-spec.json +++ b/config-provisioning/abi-spec.json @@ -506,7 +506,7 @@ ], "methods": [ "public abstract java.util.Optional getDeployment(com.yahoo.config.provision.ApplicationId)", - "public abstract java.util.Map getSupportedInfraDeployments()" + "public abstract void activateAllSupportedInfraApplications()" ], "fields": [] }, |