1
93%
main: 93%

Ran 14 Aug 2025 05:09PM UTC

Files 7

Run time 0s

Badge

Embed ▾

Committed 14 Aug 2025 05:03PM UTC coverage: 93.496%. First build

Job # 16971768607.1

Build Type

Pull #164

github

Committed by

ghukill

Commit Message

Omit chain from DuckDB S3 secret

Why these changes are being introduced:

It sounds like the best option for ECS tasks is using 'instance'
as the provider chain type, where for local dev and/or lambdas
it might be 'sso' or 'env'.  Not having 'instance' appears to cause
failures in the ECS task.

How this addresses that need:

By omitting the 'chain' option entirely from DuckDB secret creation
we allow the default provider chain to take effect.  Given our fairly
normal usage of DuckDB and S3, this is probably the best approach.

Side effects of this change:
* DuckDB to S3 connections work in ECS

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/TIMX-540

Pull Request Pull Request #164: TIMX 540 - adjust AWS credential chain for ECS context

Run Details

460 of 492 relevant lines covered (93.5%)

0.93 hits per line

MITLibraries / timdex-dataset-api / 16971768607 / 1
93%
main: 93%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16971768607.1

MITLibraries / timdex-dataset-api / 16971768607 / 1 93% main: 93%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 16971768607.1

MITLibraries / timdex-dataset-api / 16971768607 / 1
93%
main: 93%

README BADGES
x