Decouple application code from etl repository

[JimCircadian]

This will ultimately serve us well to decouple azure function app implementations from the infrastructure code, allowing devops services in azure to deploy from repositories when the perimeter is no longer directly accessible.

• [x] forecast-processor from icenetprocessor docker image / repository from the icenet-event-processor repository
  • [x] Move code out of etl codebase (docker images will update automatically on push anyway)
  • [x] Check whether additional function deployment over the top of docker image deployment works
  • [x] Define manual update process for application (just pushing docker image)
• [x] pygeoapi as its function app implementation from the icenet-geoapi repository
  • [x] Check configuration usage of environment variables
  • [x] Update deployment
  • [x] Determine github integration method / publish mechanism, implement in repository
  • [x] Test manual update
• [x] webapp/asset deployment from the icenet-application repository
  • [x] Application deployment from github via deployment center / push mechanism
  • [x] Test manual update
• [x] InputBlobTrigger from a new netcdf-geoapi-processing processing repository
  • [x] See #43

[JimCircadian]

For the apps in the geoapi and processor modules, local-exec of the az agent mean that decoupling is more complicated, as that invokes the build process within the container which we rely on. However, hopefully in all cases this can be farmed out to an action in the individual repositories. If so, we stand a much better chance of isolating the application deployments and thus securing the endpoints prior to needing to deploy, which can then be done via a bastion or VPN to satisfy #37

[JimCircadian]

Additional deployment over the top of a docker image doesn't seem to work, so abandoning that. The docker image was used thanks to the size of tensorflow binary setup and which wasn't working well with the oryx build process, so sticking with docker for the moment.

func azure functionapp publish [[REDACTED]] --python
Your functionapp is using a custom image DOCKER|registry.hub.docker.com/jimcircadian/iceneteventprocessor:latest.
Assuming that the image contains the correct framework.

Getting site publishing info...
Updating Application Settings for Remote build...
Timed out waiting for SCM to update the Environment Settings

[JimCircadian]

Sorted out a new repository for the geoapi-processing

[JimCircadian]

Confirmed that the new geoapi deployment from icenet-geoapi works using the secrets file output from terraform