move stac-data-proxy/magpie dependency to stac-data-proxy/secure-data…

…-proxy

birdhouse/optional-components/stac-data-proxy/.gitignore

@@ -1,2 +1,2 @@
-config/magpie/permissions.cfg
 config/proxy/conf.extra-service.d/stac-proxy-data.conf
+config/secure-data-proxy/permissions.cfg

birdhouse/optional-components/stac-data-proxy/config/secure-data-proxy/docker-compose-extra.yml

@@ -0,0 +1,5 @@
+version: "3.4"
+services:
+  magpie:
+    volumes:
+      - ./optional-components/stac-data-proxy/config/secure-data-proxy/permissions.cfg:${MAGPIE_PERMISSIONS_CONFIG_PATH}/stac-data-proxy.cfg:ro

birdhouse/optional-components/stac-data-proxy/config/magpie/permissions.cfg.template → birdhouse/optional-components/stac-data-proxy/config/secure-data-proxy/permissions.cfg.template

@@ -1,6 +1,6 @@
 # NOTE:
-# Assume 'secure-data-proxy' would exist if needed.
-# Since 'secure-data-proxy' < 'stac-data-proxy', it should be loaded first.
+# Assume 'secure-data-proxy' would exist if needed (other component dependency).
+# Since sorted load order of 'secure-data-proxy' < 'stac-data-proxy' in Magpie, 'secure-data-proxy' should exist.
 permissions:
   # following permission does not change anything technically (full access for admins)
   # it is employed only to set up the relevant resource path and make permission customization easier by Magpie API/UI

birdhouse/optional-components/stac-data-proxy/default.env

@@ -17,7 +17,7 @@ EXTRA_VARS='
 # adding them to 'VARS', they will also be validated in case of override of 'default.env' using 'env.local'
 VARS="$VARS $EXTRA_VARS"
 
-# Direcotry path that will be used as volume mount for storing hosted STAC assets data
+# Directory path that will be used as volume mount for storing hosted STAC assets data
 # NOTE:
 #   Hosting is not performed by the API itself. Data is expected to already reside in that
 #   location when referenced by STAC Collections and Items to make them accessible externally.