request.yaml

apiVersion: http.crossplane.io/v1alpha2
kind: Request
metadata:
  name: manage-user
spec:
  forProvider:
    # Injecting data from secrets is possible, simply use the following syntax: {{ name:namespace:key }} (supported for body and headers only)
    insecureSkipTLSVerify: true
    waitTimeout: 5m
    headers:
      Content-Type:
        - application/json
      Authorization:
        - ("Bearer {{ auth:default:token }}")
    payload:
      baseUrl: http://flask-api.default.svc.cluster.local/v1/users
      body: |
        {
          "username": "mock_user", 
          "password": "secretdata {{ user-password:crossplane-system:password }}",
          "email": "mock_user@example.com", 
          "age": 30
        }
    mappings:
      # Scenario 1: Action specified, method not specified (defaults to POST for CREATE)
      - action: CREATE
        # method: "POST" 
        body: |
          {
            username: .payload.body.username, 
            email: .payload.body.email, 
            age: .payload.body.age,
            password: .payload.body.password
          }
        url: .payload.baseUrl
        headers:
          Content-Type:
            - application/json
          Authorization:
            - ("Bearer {{ auth:default:token }}")
          Extra-Header-For-Post:
            - extra-value

      # Scenario 2: Action specified, method not specified (defaults to GET for OBSERVE)
      - action: OBSERVE
        # method: "GET"
        url: (.payload.baseUrl + "/" + (.response.body.id|tostring))

      # Scenario 3: Method specified, action not specified (PUT implies UPDATE)
      - method: "PUT"
        body: |
          {
            email: .payload.body.email, 
            age: .payload.body.age
          }
        url: (.payload.baseUrl + "/" + (.response.body.id|tostring))

      # Scenario 4: Action specified, method not specified (defaults to DELETE for REMOVE)
      - action: REMOVE
        # method: "DELETE"
        url: (.payload.baseUrl + "/" + (.response.body.id|tostring))
    
    # expectedResponseCheck is optional. If not specified or if the type is "DEFAULT", 
    # the resource is considered up to date if the GET response matches the PUT body.
    # If specified, the JQ logic determines if the resource is up to date:
    # - If the JQ query is false, a PUT request is sent to update the resource.
    # - If true, the resource is considered up to date.
    expectedResponseCheck:
      type: CUSTOM
      logic: |
        if .response.body.password == .payload.body.password
         and .response.body.age == 30
         and .response.headers."Content-Type" == ["application/json"]
         and .response.headers."X-Secret-Header"[0] == "{{ response-secret:default:extracted-header-data }}"
         then true 
         else false 
         end

    # Secrets receiving patches from response data
    secretInjectionConfigs: 
      - secretRef:
          name: response-secret
          namespace: default
        secretKey: extracted-user-email
        responsePath: .body.email
        # setOwnerReference determines if the secret should be deleted when the associated resource is deleted.
        # When injecting multiple keys into the same secret, ensure this field is set consistently for all keys.        
        setOwnerReference: true
      - secretRef:
          name: response-secret
          namespace: default
        secretKey: extracted-header-data
        responsePath: .headers."X-Secret-Header"[0]
        setOwnerReference: true
      - secretRef:
          name: response-user-password
          namespace: default
        secretKey: extracted-user-password
        responsePath: .body.password
  providerConfigRef:
    name: http-conf