Simon Hartcher
303af8661c
fix: make modules depend on codegen
2025-03-13 14:32:03 +11:00
8c68dd6902
add support for raw responses beginning with name of single field in response struct
2025-02-05 13:24:09 -08:00
96e2b7bbc1
support for timestamp as f128 (more)
...
f128 is not really the correct data type long term. More information on the exact details are
https://smithy.io/2.0/aws/protocols/aws-json-1_1-protocol.html and
https://smithy.io/2.0/spec/protocol-traits.html\#timestampformat-trait
But...it will hold all our values and parses correctly, so we can use it for now
2025-02-05 13:23:55 -08:00
acd6589909
add support for raw responses beginning with name of single field in response struct
2025-02-05 13:22:52 -08:00
78b36e2316
support for timestamp as f128 (more)
...
f128 is not really the correct data type long term. More information on the exact details are
https://smithy.io/2.0/aws/protocols/aws-json-1_1-protocol.html and
https://smithy.io/2.0/spec/protocol-traits.html\#timestampformat-trait
But...it will hold all our values and parses correctly, so we can use it for now
2025-02-05 13:21:53 -08:00
97b784f8e3
cleanup main, re-enable riscv64-linux
2024-10-17 12:00:20 -07:00
3d78705ea5
update to latest zig nominated
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Failing after 26s
aws-zig nightly build / build-zig-nightly (push) Failing after 3m36s
2024-10-17 10:54:01 -07:00
908c9d2d42
add diagnostics option to rest calls
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m30s
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Failing after 35s
aws-zig nightly build / build-zig-nightly (push) Failing after 39s
2024-08-27 13:37:36 -07:00
1fdff0bacd
include credenitals in logging control (tie to signing)
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m31s
2024-08-27 11:42:07 -07:00
1fe39007c5
add logging control useful for build scripts
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m32s
2024-08-27 11:30:23 -07:00
c5cb3dde29
Remove extra fields in request (AWS is sensitive to them)
2024-08-27 10:40:52 -07:00
c056dbb0ff
add diagnostics for failures
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m31s
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Successful in 1m30s
aws-zig nightly build / build-zig-nightly (push) Failing after 26s
2024-08-23 16:03:37 -07:00
9e8198cee4
also override iam region for signing requests
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m29s
2024-08-23 14:49:19 -07:00
43238a97eb
add iam global endpoint exception
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m29s
2024-08-23 14:40:56 -07:00
238952d127
add iam getRole test
...
This test triggers the scenario that a required response element exists, which
forces our check for "we do not expect data for this call" to be comptime.
It previously was accidentally runtime, which was solved by making
expected_body_field_len a comptime var.
2024-08-23 12:53:58 -07:00
e5b662873a
omit most automatically added headers
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m28s
2024-08-19 09:42:00 -07:00
a9f99c0205
add failing test for duplicate header values
2024-08-19 09:41:39 -07:00
3e89ec468a
utf16leToUtf8 -> utf16LeToUtf8 (capital L)
AWS-Zig Build / build-zig-amd64-host (push) Successful in 3m11s
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Successful in 3m13s
aws-zig nightly build / build-zig-nightly (push) Failing after 2m39s
2024-07-01 14:18:40 -07:00
f558b058e1
use explicit splitScalar
AWS-Zig Build / build-zig-amd64-host (push) Successful in 3m6s
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Successful in 3m7s
aws-zig nightly build / build-zig-nightly (push) Failing after 48s
2024-07-01 13:45:29 -07:00
a659c99350
re-enable windows test for 0.13/LLVM 18, update README
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Successful in 3m5s
aws-zig nightly build / build-zig-nightly (push) Successful in 3m32s
2024-06-04 17:34:33 -07:00
7d80f42a3e
update to zig 0.13-dev.365 (zig nominated build 2024.05)
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Failing after 1m57s
aws-zig nightly build / build-zig-nightly (push) Failing after 3m49s
2024-06-04 14:53:09 -07:00
c60c40f627
we are not mutating headers, so do not ask for mutable headers
AWS-Zig Build / build-zig-amd64-host (push) Successful in 3m3s
2024-05-15 13:47:33 -07:00
99a61c0bd2
update aws-zig to zig 0.12.0 (example will still fail)
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 2m25s
2024-04-22 08:23:01 -07:00
e74a0e9456
get build LLVM-approved (riscv64-linux disabled for now)
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Failing after 3m8s
aws-zig nightly build / build-zig-nightly (push) Failing after 1m0s
2024-04-02 17:49:45 -07:00
e6634d3c0f
shell32 has been removed, use USERPROFILE env var instead
aws-zig mach nominated build / build-zig-nightly (push) Failing after 1h21m14s
aws-zig nightly build / build-zig-nightly (push) Failing after 10m24s
2024-04-02 11:05:17 -07:00
7dcf3d3a2e
upgrade to nominated zig 2024.3.0-mach (0.12.0-dev.3180+83e578a18)
...
aws-zig mach nominated build / build-zig-nightly (push) Failing after 28m36s
aws-zig nightly build / build-zig-nightly (push) Failing after 57s
There were significant changes to the way HTTP operates since 0.11,
effecting client operations, but more substantially, the server
implementation, which effected the test harness.
std.http.Headers was removed, including the getFirstValue function, which
needed to be replicated. On the plus side, a std.http.Header struct was
added, identical to our own structure, so I have removed out own header
in favor of stdlib.
On the Http client side, I have switched to use the fetch API. Proxy
support is built in, but we are using (mostly) our own implementation
for now, with the remaining conversion left as a TODO item. Raw URIs are
now supported, so the workaround for issue 17015 has been removed. Large
payloads should also be fixed, but this has not been tested.
The standard library now adds the content-length header
(unconditionally), which is a decision of dubious nature. I have removed
the addition of content-length, which also means it is not present
during signing. This should be allowed.
Dependency loop on fieldTransformer was fixed. This should have been
a problem on zig 0.11, but was not. This effected the API for the json
parsing, but we were not using that. At the call site, these did not
need to be specified as references.
With the http server no longer doing all the allocations it once was,
the test harness now has a lot more allocations to perform. To alleviate
the bookeeping, this was moved to an Arena allocator. The client,
which is really what is under test, continues to use the allocator
passed.
2024-04-02 09:27:42 -07:00
6df02b1074
switch sqs query test (json) with sts query test (xml) and fix response parsing
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m22s
2024-02-29 20:41:03 -08:00
55298f7575
skip sqs, which changed from query to json protocol, and update S3 test
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 4m18s
2024-02-29 16:59:10 -08:00
31324c7e83
support for server verification of clients that do not pass x-amz-content-sha256
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m17s
2024-02-24 09:43:36 -08:00
melhindi
7a5fa0bb2e
Replace var with const where applicable
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m37s
2024-01-18 13:43:45 +01:00
14666da73f
clean up build (includes two fixes for arm 32 bit)
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 5m38s
2024-01-09 15:22:03 -08:00
d08d0f338f
Using ".?" actually causes a panic, which we do not want in this path
...
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m20s
NOTE: This only fixes the top level Authorization header. A malformed
header can still cause havoc
2023-10-25 00:00:11 -07:00
825d93720a
add verifiyServerRequest/change verify to WASM-friendly type
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 8m20s
2023-10-22 10:25:07 -07:00
ed96e2ff66
support for >16KiB requests
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m44s
2023-10-21 10:20:09 -07:00
db19041b96
fix memory leak when AWS_ENDPOINT_URL is used
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m4s
2023-09-15 09:05:53 -07:00
f8b6b3e521
make aws_signing module ready
2023-09-14 14:06:35 -07:00
ff1e6f4cf3
aws_signing: provide signing verification based on a server http request
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m41s
2023-09-08 21:45:36 -07:00
0e48c6f79b
clean up test logging/add header logging in test
2023-09-08 21:43:20 -07:00
6ae8b68786
allow static signing iime in aws.zig/use static time for testing
2023-09-08 21:42:38 -07:00
037fb7f1ae
allow aws_http to use static signing time
2023-09-08 21:41:08 -07:00
fd0e80f00c
allow datetime to timestamp conversion from outside date.zig
2023-09-08 21:40:03 -07:00
67b24641e2
allow trailing Z on iso 8601 parsing
2023-09-08 21:39:19 -07:00
2d42bbf464
comment date logging functions so type can be used at comptime
2023-09-08 21:38:28 -07:00
6755099c36
apparently we do need that check?
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m36s
2023-08-30 13:49:56 -07:00
fb34e556f7
re-enable demo code
2023-08-30 13:49:29 -07:00
d82728602b
fix failing test
2023-08-30 13:40:08 -07:00
d50503a2f8
initial commit on code to work around 17015. Sourced from std lib
2023-08-30 13:32:27 -07:00
55f662f5d7
add failing test for double encoding issue
2023-08-30 12:59:10 -07:00
f2a3a967c7
add comment to indicate root cause of the tagResource issue
2023-08-30 12:55:40 -07:00
c011f1d7f9
update user agent (we have not used AWS Common Runtime for a while
2023-08-30 12:55:06 -07:00
