Respond with a 401 rather than attempting to redirect (#154)

Author: Aaron Suarez

kubernetes/operationcode_python_backend/overlays/staging/ingress.yaml

@@ -10,7 +10,7 @@ metadata:
     alb.ingress.kubernetes.io/scheme: internet-facing
     alb.ingress.kubernetes.io/ssl-policy: ELBSecurityPolicy-TLS-1-2-2017-01
     alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
-    alb.ingress.kubernetes.io/actions.redirect-to-root: '{"Type":"redirect","RedirectConfig":{"Host":"resources.staging.operationcode.org","Path":"/","Port":"443","Protocol":"HTTPS","StatusCode":"HTTP_302"}}'
+    alb.ingress.kubernetes.io/actions.response-401: '{"Type":"fixed-response","FixedResponseConfig":{"ContentType":"text/plain","StatusCode":"401","MessageBody":"401 Not Authorized"}}'
   labels:
     app: back-end
 spec:
@@ -43,11 +43,11 @@ spec:
       paths:
       - path: /metrics
         backend:
-          serviceName: redirect-to-root
+          serviceName: response-401
           servicePort: use-annotation
       - path: /healthz
         backend:
-          serviceName: redirect-to-root
+          serviceName: response-401
           servicePort: use-annotation
       - path: /*
         backend: