docs: EA-Updates-1-27-26

content/3.genomics-platform/1.getting-started/2.accounts-and-billing.md

@@ -5,7 +5,7 @@ description: Information on account creation and billing setup.
 St. Jude Cloud is built on top of [DNAnexus](https://www.dnanexus.com/), a data-analysis and management platform that specializes in the field of bioinformatics.
 All of our account management is shared between St. Jude Cloud and DNAnexus.
 
-### Creating a St. Jude Cloud Account
+## Creating a St. Jude Cloud Account
 
 To create an account, simply navigate to [Genomics Platform](https://platform.stjude.cloud) and then select “Log In.”
 
@@ -23,7 +23,7 @@ Users who have an existing DNAnexus account must use the St. Jude Cloud account
 Once you have created an account through St. Jude Cloud your DNAnexus account and St. Jude Cloud account will be linked going forward.
 ::
 
-### Billing Setup
+## Billing Setup
 
 If you are a St. Jude employee, go to the [Bioinformatics Self Service page](https://sjcrh.sharepoint.com/sites/computational-biology/SitePages/Bioinformatics-Self-Service-on-St.-Jude-Cloud.aspx) on the Intranet for information on how to set up your billing account.
 

content/3.genomics-platform/3.managing-data/5.renewing-your-daa.md

@@ -4,12 +4,22 @@ navigation:
   title: Renewing Your DAA
 ---
 
+## Renewing Your Data Access Agreement
+
 The St. Jude Cloud [Data Access Agreement (DAA)](/genomics-platform/getting-started/glossary#data-access-agreement) is only valid for one year after the date it was approved.
 When your DAA is about to expire, you will get an automated email from [notifications@stjude.cloud](mailto:notifications@stjude.cloud) with the name of the DAA that is expiring and a link to the St. Jude Cloud Extension Addendum.
-
 In order to extend your DAA, you must fill out an Extension Addendum.
 The Extension Addendum will extend the previous agreement for an additional year.
-Please note that if you do not fill out an Extension Addendum, you will be expected to delete all copies of the data subject to the expiring agreement.
+
+* If your institution is within the United States, you will have the option to complete the Extension Addendum via DocuSign.
+* If your institution is not within the United States, you will complete the Extension Addendum manually by downloading the form and following the steps outlined below.
+
+::callout{icon="i-heroicons-exclamation-circle" color="blue"}
+**Note**  
+If you do not fill out an Extension Addendum, you will be expected to delete all copies of the data subject to the expiring agreement.
+::
+
+## Completing the Form Manually
 
 Follow the steps below to ensure that you have accurately filled out all sections of the Extension Addendum.
 
@@ -42,7 +52,7 @@ Follow the steps below to ensure that you have accurately filled out all section
 
 ::callout{icon="i-heroicons-exclamation-circle" color="orange"}
 **St. Jude Employees**<br>
-This section is not applicable for St. Jude employees.
+The Information Security Officer section is not applicable for St. Jude employees.
 ::
 
 * The bottom section of page 3 is for St. Jude to sign and date.

deployment/preview/pr132/app.yaml

@@ -0,0 +1,87 @@
+apiVersion: helm.toolkit.fluxcd.io/v2beta1
+kind: HelmRelease
+metadata:
+  name: docs
+  namespace: docs-pr132
+spec:
+  interval: 30m
+  chart:
+    spec:
+      chart: generic
+      version: 1.1.x
+      sourceRef:
+        kind: HelmRepository
+        name: stjudecloud
+        namespace: flux-system
+      interval: 1h
+  values:
+    nameOverride: docs
+    extraDeploy:
+      - |
+        apiVersion: v1
+        kind: Service
+        metadata:
+          name: {{ template "common.names.fullname" . }}-oauth-bridge
+          labels: {{- include "common.labels.standard" . | nindent 4 }}
+            {{- if .Values.commonLabels }}
+            {{- include "common.tplvalues.render" ( dict "value" .Values.commonLabels "context" $ ) | nindent 4 }}
+            {{- end }}
+          {{- if .Values.commonAnnotations }}
+          annotations: {{- include "common.tplvalues.render" ( dict "value" .Values.commonAnnotations "context" $ ) | nindent 4 }}
+          {{- end }}
+        spec:
+          type: ExternalName
+          externalName: oauth2-proxy.oauth2-proxy
+      - |
+        ---
+        apiVersion: networking.k8s.io/v1
+        kind: Ingress
+        metadata:
+          name: {{ .Release.Name }}-oauth
+        spec:
+          ingressClassName: nginx
+          rules:
+          - host: {{ .Values.ingress.hostname }}
+            http:
+              paths:
+                - backend:
+                    service:
+                      name: {{ template "common.names.fullname" . }}-oauth-bridge
+                      port:
+                        number: 80
+                  path: /oauth2
+                  pathType: ImplementationSpecific
+          tls:
+          - hosts:
+            - {{ .Values.ingress.hostname }}
+            secretName: {{ .Values.ingress.hostname }}-tls
+    image:
+      repository: stjudecloud/docs
+      tag: pr132-ce80daf-243 # {"$imagepolicy": "flux-system:docs-pr132:tag"}
+    podAnnotations:
+      linkerd.io/inject: enabled
+      config.linkerd.io/proxy-cpu-request: 20m
+    containerPorts:
+      http: 3000
+    service:
+      ports:
+        - name: http
+          protocol: TCP
+          port: 3000
+          targetPort: http
+    ingress:
+      enabled: true
+      hostname: docs-pr132.staging.stjude.cloud
+      path: /
+      annotations:
+        cert-manager.io/cluster-issuer: letsencrypt-prod
+        linkerd.io/inject: ingress
+        nginx.ingress.kubernetes.io/auth-signin: https://$host/oauth2/start?rd=$escaped_request_uri
+        nginx.ingress.kubernetes.io/auth-url: https://$host/oauth2/auth
+        nginx.ingress.kubernetes.io/service-upstream: "true"
+        nginx.ingress.kubernetes.io/enable-modsecurity: "true"
+        nginx.ingress.kubernetes.io/enable-owasp-core-rules: "true"
+      tls:
+        enabled: true
+    datadog:
+      enabled: false