Skip to content

Mod/settings update #4625

Open
boozallendanny wants to merge 19 commits into
qatfrom
mod/settings-update-fapc
Open

Mod/settings update #4625
boozallendanny wants to merge 19 commits into
qatfrom
mod/settings-update-fapc

Conversation

@boozallendanny

Copy link
Copy Markdown
Contributor

Description:

Update data dictionary s3 location and key to use env vars if they exist

Technical Details:

Requirements for PR Merge:

  1. Unit & integration tests updated
  2. API documentation updated (examples listed below)
    1. API Contracts
    2. API UI
    3. Comments
  3. Data validation completed (examples listed below)
    1. Does this work well with the current frontend? Or is the frontend aware of a needed change?
    2. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
    3. Is the expected data returned with the expected format?
  4. Appropriate Operations ticket(s) created
  5. Jira Ticket(s)
    1. DEV-0

Explain N/A in above checklist:

@boozallendanny boozallendanny changed the base branch from master to qat April 8, 2026 18:05
@boozallendanny boozallendanny added the do not merge [PR] shouldn't be merged label Apr 20, 2026
@boozallendanny boozallendanny changed the title Mod/settings update fapc Mod/settings update Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge [PR] shouldn't be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants