You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
at present we are presuming that the system will be brought up along side the EOI services, this might not be the case. we could do with a method of bringing up the coi-service separate from the eoi services then sync the dataset resources after the fact.
i think this might be done via a resources registry pass for datasets, then following the model of table loader to generate the resources in postgres and geoserver.
My guess is that this would be request driven, maybe started by importerservice?
This would also be important to run if the data services get out of sync for any reason.
we would test this on the deployed infrastructure (vms) by:
preloading a coi-services vm (eoi-dev1) with alpha or beta
bring up all eoi services on second instance (test-pg-03)
run method to sync the services
The text was updated successfully, but these errors were encountered:
at present we are presuming that the system will be brought up along side the EOI services, this might not be the case. we could do with a method of bringing up the coi-service separate from the eoi services then sync the dataset resources after the fact.
i think this might be done via a resources registry pass for datasets, then following the model of table loader to generate the resources in postgres and geoserver.
My guess is that this would be request driven, maybe started by
importerservice
?This would also be important to run if the data services get out of sync for any reason.
we would test this on the deployed infrastructure (vms) by:
The text was updated successfully, but these errors were encountered: