Add request header configuration to admin dataset source interface

[Copilot]

Request header configuration was only available in the Visual Data Editor. Admin users working in /admin/dataset-source lacked access to configure authentication headers for dataset downloads.

Changes

JSP View (dataset-source.jsp)

• Added Request Headers fieldset with dynamic header management
• JavaScript handles initialization from existing JSON, add/remove rows, and serialization on submit
• Foundation grid layout (5-6-1) matches existing admin forms

Widget Controller (DatasetSourceWidget.java)

• Added dataset.setRequestConfig(context.getParameter("requestConfig")) to updateSettings() and downloadRemoteFileAction() methods
• Headers persist with both "Save" and "Save & Download Remote File" actions

Implementation

Headers stored as JSONB and automatically used by existing DatasetDownloadRemoteFileCommand:

{
  "headers": {
    "Authorization": "******",
    "X-API-Key": "abc123xyz"
  }
}

UI provides empty state, dynamic add/remove, and HTML escaping. Backend integration leverages existing infrastructure - no changes needed to download logic.

Original prompt

In the Visual Data Editor, users can choose a URL to download data from and synchronize the datasets with... but extra inputs might be needed for Request Headers like an access token or other values. Extend the datasets database with a JSONB field for storing request information, and make the dynamic form for entering the values. Information could include Request Method and OUATH sequence.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.