Skip to content

BCDA-10439: LEAD aco config for lower envs - #1528

Merged
bhagatparwinder merged 5 commits into
mainfrom
parwinder/BCDA-10439-lead-aco-config-lower-envs
Nov 9, 2026
Merged

bhagatparwinder merged 5 commits into
mainfrom
parwinder/BCDA-10439-lead-aco-config-lower-envs

Conversation

@bhagatparwinder

@bhagatparwinder bhagatparwinder commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

🎫 Ticket

https://jira.cms.gov/browse/BCDA-10439

🛠 Changes

  • Add config (to dev and test) env for LEAD and update tests
    • Correctly set performance_year_transition and lookback_period
    • Deny v1/v2 access
  • Update parser to handle new CCLF file format and associated tests

ℹ️ Context

Onboarding new CMS model entity (LEAD)

🧪 Validation

Unit tests and linter pass.

@laurenkrugen-navapbc

Copy link
Copy Markdown
Contributor

should we be updating our integration test with our various models' attribution files?

@bhagatparwinder
bhagatparwinder merged commit 402868b into main Nov 9, 2026
11 checks passed
@bhagatparwinder
bhagatparwinder deleted the parwinder/BCDA-10439-lead-aco-config-lower-envs branch November 9, 2026 17:54
@bhagatparwinder

bhagatparwinder commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor Author

should we be updating our integration test with our various models' attribution files?

Good point. Let me check what that entails. If I can squeeze it into the next ticket for AHEAD onboarding, I will. Otherwise, I will create a follow-up ticket.

Edit: Took a look at integration tests. @laurenkrugen-navapbc We shouldn't need to update the integration tests for new models unless we ingest attribution files in a way that is different. AHEAD uses standard CCLF files, the end-to-end pipeline is already verified by the A0001 test.

The only model-specific logic for CCLF models is the filename pattern matching, which is fully covered by unit tests.

This branch was successfully deployed

1 active deployment
test — a6b61b22 Deployed Nov 6, 2026 by bhagatparwinder via trigger #401
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants