Commit graph

639 commits

Author SHA1 Message Date
5c7aed071f
switch to http status enum
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m10s
2026-02-04 00:37:27 -08:00
c1df6ef3a6
avoid outputting errors if diagnostics field provided
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m13s
2026-02-03 15:30:59 -08:00
fd568f26b9
refactor rest calls so all fields are included appropriately
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 13m25s
2026-02-02 18:00:00 -08:00
4df27142d0
fix issue with config file reading the wrong options
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 14m17s
2026-02-02 17:11:44 -08:00
31240cd21e
provide consumers a way to change order of precedence based on cli flag 2026-02-02 17:11:18 -08:00
686b18d1f4
use profile_name in credential options
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m6s
2026-02-02 16:13:09 -08:00
742a820eeb
add credential options to aws options so profile can be passed 2026-02-02 16:11:03 -08:00
6e34e83933
do not emit null optional fields
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 15m4s
2026-02-01 17:47:51 -08:00
fdc2089969
remove build.zig aws constant
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m5s
This was always problematic, and bypasses the build system. It broke earlier
when moving to proper modules, and really, it is not worth using. The idea was
to allow usage of the SDK in a build context, but that does not work anyway,
because the build operates in a sandboxed environment that effectively bars
things like connecting to TLS endpoints. That is a feature of the build system,
not a bug, and issues like https://github.com/ziglang/zig/issues/14286
demonstrate that the zig team wants to sandbox even further. For downstream,
the right idea here is actually to create an executable that depends on aws
and run it as part of the build. This is where https://git.lerch.org/lobo/lambda-zig
is heading.
2026-01-30 12:04:30 -08:00
f788eed35c
update example 2026-01-30 11:58:27 -08:00
b4eddb6f82
update example 2026-01-30 10:01:52 -08:00
efdef66fdb
bifrucate the service_model module based pre-packaging
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m2s
2026-01-30 09:38:10 -08:00
615f92c654
glob expansion needs to be in target dir
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 15m54s
2026-01-30 08:41:06 -08:00
4fed9954cb
avoid ./ prefix on tar paths
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 7m41s
See https://github.com/ziglang/zig/issues/23152
2026-01-30 08:31:16 -08:00
df963c5316
fix project packaging
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m2s
I believe this broke in 4a6c84e, but have not bisected.
2026-01-29 15:35:11 -08:00
d4fdd74f5b
uncomment pub const aws in build.zig as this seems to be fixed in 0.15.2
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 9m12s
2026-01-29 15:06:28 -08:00
6d80c2f56b
remove message about zig nightly - issue is resolved
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m28s
2025-11-15 11:22:09 -08:00
0dc0154c16
Revert "temporary force nightly to home server"
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 8m46s
This reverts commit 79213a991d.
2025-11-15 11:12:25 -08:00
79213a991d
temporary force nightly to home server
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m46s
On the home server, git.lerch.org will resolve to
an A record (split-horizon DNS). This works around
https://github.com/ziglang/zig/issues/25811.
2025-11-06 13:08:21 -08:00
0e63e501db
add note about nightly build
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m48s
2025-11-06 12:37:30 -08:00
30a8a926a4
update example dependency (dep should handle current nightly + 0.15.1)
All checks were successful
aws-zig nightly build / build-zig-nightly (push) Successful in 9m0s
AWS-Zig Build / build-zig-amd64-host (push) Successful in 9m24s
2025-09-03 16:53:58 -07:00
4c29d28805
Revert "switch example depedendency based on zig version"
This reverts commit 5bfcd10519.
2025-09-03 16:51:44 -07:00
5bfcd10519
switch example depedendency based on zig version
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 9m18s
aws-zig nightly build / build-zig-nightly (push) Successful in 8m32s
2025-09-03 14:53:51 -07:00
e41f98b389
adopt to changed signature for readFileAlloc in nightly
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Successful in 14m58s
aws-zig nightly build / build-zig-nightly (push) Failing after 28m7s
2025-09-03 14:08:27 -07:00
5ba3be2cc4
move off of deprecated APIs 2025-09-03 14:00:36 -07:00
dafc69726f
handle http headers with value lists
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 9m11s
aws-zig nightly build / build-zig-nightly (push) Successful in 8m49s
2025-08-29 15:00:27 -07:00
f0f7b180c4
ignoring json.zig in zlint as it was imported from stdlib 2025-08-29 14:02:52 -07:00
0dcdba7887
add zls 0.15.0 to mise config 2025-08-29 13:54:41 -07:00
a487d6c2e7
update setup-zig on nightly to 2.0.5
All checks were successful
aws-zig nightly build / build-zig-nightly (push) Successful in 15m28s
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m43s
2025-08-25 17:32:42 -07:00
8f3ca1d9cd
fix remaining signature tests
Some checks failed
aws-zig nightly build / build-zig-nightly (push) Failing after 52s
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m55s
2025-08-25 17:25:08 -07:00
b1a096fa1e
update example to latest working lib
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m42s
2025-08-25 14:25:56 -07:00
fd30c9f870
remove caveat in readme. we should be gtg 2025-08-25 14:16:30 -07:00
cfc8aee1a6
a lot of test code, plus a one line ".deinit()" fix
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m39s
2025-08-25 14:14:15 -07:00
214c580db4
get failing live request under unit test 2025-08-25 13:07:46 -07:00
2fab8ac0b8
add note regarding 0.15.1 status
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m43s
2025-08-25 11:08:48 -07:00
ffdd31d7b0
upgrade example to 0.15.1
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 7m51s
2025-08-25 10:39:29 -07:00
e29829f2a0
fix failing s3 test
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 6m25s
Not quite sure the problem I saw earlier in aws.zig, but the data
entering that switch prong is []const u8, so it is fine for what we are
doing
2025-08-25 10:00:50 -07:00
74704506d8
update tests for zig 0.15.1
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 1m41s
This removes the need to spin up a web server for each test, instead,
mocking the necessary methods to do everything in line. This will make
the tests much more resilient, and with the remaining WriterGate changes
expected in zig 0.16, I suspect the mocking will be unnecessary in the
next release.

There are several test issues that remain:

* Two skipped tests in signature verification. This is the most
  concerning of the remaining issues
* Serialization of [][]const u8 was probably broken in zig 0.14.1, but
  the new version has surfaced this issue. Warning messages are being
  sent, and this needs to be tracked down
* One of the tests is failing as S3 storage tier extra header is not
  being offered. I'm not sure what in the upgrade might have changed
  this behavior, but this needs to be investigated
2025-08-24 15:56:36 -07:00
1e8756cc9a
fix runtime panics, set tests to skip for now 2025-08-23 13:34:36 -07:00
b126ec25e8
fix aws.zig tests 2025-08-23 10:56:21 -07:00
b2ce163b6f
fix aws.zig and url.zig tests, simplify url testing and skip 1 test for now 2025-08-23 10:45:35 -07:00
90c5efcace
clean up all the basic things 2025-08-23 09:44:34 -07:00
0a0933e38f
move test suite to its own file 2025-08-23 09:20:22 -07:00
1170ba99fc
fix most test compilation errors 2025-08-23 08:48:32 -07:00
8d399cb8a6
zig build compiles using zig 0.15.1
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 2m27s
2025-08-22 18:00:34 -07:00
5334cc3bfe
writer needs to be a constant to the pointer of the writer field 2025-08-22 13:30:09 -07:00
53ac60c875
don't forget to flush! 2025-08-22 12:52:57 -07:00
5541742db3
update README to reflect new zig
Some checks failed
AWS-Zig Build / build-zig-amd64-host (push) Failing after 1m10s
2025-08-22 11:47:02 -07:00
b865285b24
update codegen to 0.15.1 2025-08-22 11:23:26 -07:00
9ed9c9b447
update dependencies 2025-08-22 11:22:58 -07:00