Commit graph

99 commits

Author SHA1 Message Date
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
908c9d2d42
add diagnostics option to rest calls 2024-08-27 13:37:36 -07:00
1fdff0bacd
include credenitals in logging control (tie to signing) 2024-08-27 11:42:07 -07:00
1fe39007c5
add logging control useful for build scripts 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 2024-08-23 16:03:37 -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
a9f99c0205
add failing test for duplicate header values 2024-08-19 09:41:39 -07:00
a659c99350
re-enable windows test for 0.13/LLVM 18, update README 2024-06-04 17:34:33 -07:00
99a61c0bd2
update aws-zig to zig 0.12.0 (example will still fail) 2024-04-22 08:23:01 -07:00
e74a0e9456
get build LLVM-approved (riscv64-linux disabled for now) 2024-04-02 17:49:45 -07:00
7dcf3d3a2e
upgrade to nominated zig 2024.3.0-mach (0.12.0-dev.3180+83e578a18)
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 2024-02-29 20:41:03 -08:00
55298f7575
skip sqs, which changed from query to json protocol, and update S3 test 2024-02-29 16:59:10 -08:00
melhindi
7a5fa0bb2e Replace var with const where applicable 2024-01-18 13:43:45 +01:00
14666da73f
clean up build (includes two fixes for arm 32 bit) 2024-01-09 15:22:03 -08: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
55f662f5d7
add failing test for double encoding issue 2023-08-30 12:59:10 -07:00
0a1de2b967
support chunked transfer encoding to create failing test 2023-08-29 11:56:23 -07:00
70bd8dafa5
add more information on unexpected response 2023-08-29 11:56:01 -07:00
48fc41c4b8
return cleaner error when response not expected 2023-08-29 11:30:21 -07:00
812ad96a66
add proxy support 2023-08-29 11:24:34 -07:00
591f4c43e0
all services from main.zig now under test 2023-08-28 17:49:30 -07:00
c8cba54fe0
ec2_query_with_input under test 2023-08-28 13:30:39 -07:00
6d3e820bd1
add ec2_query_no_input 2023-08-28 13:10:16 -07:00
eafb62aee9
fix leaks/re-enable rest_json_1 tests 2023-08-28 12:37:34 -07:00
827c90ab8a
add rest json tests (skippped -still leaky 2023-08-27 23:20:07 -07:00
edf931f827
add json_1_1_query_no_input: ecs listClusters runtime 2023-08-27 21:53:39 -07:00
2718e064cd
add json_1_1_query_with_input: ecs listClusters runtime 2023-08-27 21:48:27 -07:00
298a15a656
add json_1_0_query_no_input: dynamodb listTables runtime 2023-08-27 21:35:31 -07:00
10e44aa751
add json 1.0 query with input/dynamodb listTables 2023-08-27 21:26:37 -07:00
98d27b3145
add sqs listQueues call and request method/target testing 2023-08-27 19:55:45 -07:00
17ff6d3e82
clean up test code in prep for other main stuff 2023-08-27 18:12:32 -07:00
06429e0853
re-enable full demo code 2023-08-27 17:36:26 -07:00
8361431754
clean up/add credential handling 2023-08-27 15:24:58 -07:00
ae07f82dd5
disable ec2_query demos temporarily 2023-08-27 11:40:56 -07:00
b2bd779de7
re-enable whatever test that was 2023-08-27 11:03:38 -07:00
18a0ed5ce4
refalldecls for referenced dependencies 2023-08-27 11:01:40 -07:00
c84baf5152
address test leaks 2023-08-27 10:53:51 -07:00
1c072c454d
fix crash. leaks remain 2023-08-27 10:34:39 -07:00
1ba69e38ed
unit test crashing and leaky, but not failing 2023-08-27 10:29:01 -07:00
4bc8889d32
fix more compile errors - leaving 2 nasty ones 2023-08-05 16:26:09 -07:00
e49ed1b7ad
found fix for comptime decl stuff, avoid more codegen changes 2023-08-05 13:00:55 -07:00
5ee53a493d
some codegen changes needed/investigation into http_query (see note)
This fixes main compile issues. Problems that remain:

* json is borked for objects with key/value keys that need to be coerced
* currently all request structures need an http_query declaration, and this may be a hard requirement
* need to revisit all the places where we are reading http response bodies
* there are 35 compile errors that do not have reference traces and will take a while to track down
2023-08-05 12:41:04 -07:00
e6f7ab003d
zig fmt to take care of easy stuff 2023-08-04 10:07:58 -07:00
cfdf4a3141
these are old changes, but I believe part of 0.11 from a while back 2023-08-04 10:06:54 -07:00
8d852e8084
handle s3 key paths 2022-06-29 09:24:16 -07:00
247a236ad1
reduce debug logging noise 2022-06-05 18:27:36 -07:00