disposablerequest.yaml

apiVersion: http.crossplane.io/v1alpha2
kind: DisposableRequest
metadata:
  name: send-notification
spec:
  deletionPolicy: Orphan
  forProvider:
    # Injecting data from secrets is possible, simply use the following syntax: {{ name:namespace:key }} (supported for body and headers only)
    url:  http://flask-api.default.svc.cluster.local/v1/notify
    method: POST
    body: |
      {
        "recipient": "user@example.com",
        "subject": "Alert",
        "message": "Your action is required immediately."
      }
    headers:
      Content-Type:
        - application/json
      Authorization:
        - "Bearer {{ auth:default:token }}"
    insecureSkipTLSVerify: true

    # The 'expectedResponse' field is optional. If used, also set 'rollbackRetriesLimit', which determines the number of HTTP requests to be sent until the jq query returns true.
    expectedResponse: '.body.status == "sent"'
    rollbackRetriesLimit: 5
    waitTimeout: 5m

    # Indicates whether the reconciliation should loop indefinitely. If `rollbackRetriesLimit` is set and the request returns an error, it will stop reconciliation once the limit is reached.
    # shouldLoopInfinitely: true

    # Specifies the duration after which the next reconcile should occur.
    # nextReconcile: 3m 

    # Secrets receiving patches from response data
    secretInjectionConfigs: 
      - secretRef:
          name: notification-response
          namespace: default
        metadata:
          labels:
            status: .body.status
          annotations:
            key: value
        keyMappings:
          - secretKey: notification-status
            responseJQ: .body.status
          - secretKey: notification-id
            responseJQ: .body.id
        # setOwnerReference determines if the secret should be deleted when the associated resource is deleted.
        setOwnerReference: true
 
  providerConfigRef:
    name: http-conf
# TODO: check if it's possible to modify the deletionPolicy to be orphan by default.