Commit graph

20 commits

Author SHA1 Message Date
1fdff0bacd
include credenitals in logging control (tie to signing)
All checks were successful
AWS-Zig Build / build-zig-amd64-host (push) Successful in 1m31s
2024-08-27 11:42:07 -07:00
99a61c0bd2
update aws-zig to zig 0.12.0 (example will still fail)
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 2m25s
2024-04-22 08:23:01 -07:00
e6634d3c0f
shell32 has been removed, use USERPROFILE env var instead
Some checks failed
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)
Some checks failed
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
melhindi
7a5fa0bb2e Replace var with const where applicable
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m37s
2024-01-18 13:43:45 +01:00
7c40549200
cast two more content_length u64 to usize
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 4m12s
2023-08-27 15:43:40 -07:00
8361431754
clean up/add credential handling
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 1m26s
2023-08-27 15:24:58 -07:00
06040ac649
you CAN fix stupid! 2023-08-27 10:53:30 -07:00
a3fd680ea6
comment log_level for tests 2023-08-27 09:23:38 -07:00
db82116103
cast to usize for non 64 bit targets
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 4m10s
2023-08-15 08:41:06 -07:00
9e02196dd0
clean compile on 0.11, not yet fully functional
Some checks failed
AWS-Zig Build / build-zig-0.9-amd64-host (push) Failing after 1m41s
2023-08-14 10:06:28 -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
5bb382bda3
implement container credentials
All checks were successful
continuous-integration/drone/push Build is passing
2022-02-09 11:46:53 -08:00
5f3a201ffd
initial IMDSv2 implementation
All checks were successful
continuous-integration/drone/push Build is passing
2022-02-08 22:37:38 -08:00
b53cbc3ea5
support file-based credentials
All checks were successful
continuous-integration/drone/push Build is passing
2022-01-31 09:01:30 -08:00
e7734281c3
add comment about AWS_SECURITY_TOKEN 2022-01-21 06:41:10 -08:00
a667dc09d1
support for STS tokens
All checks were successful
continuous-integration/drone/push Build is passing
2022-01-20 19:42:55 -08:00
691a32d719
credential cleanup/working on Windows
Some checks failed
continuous-integration/drone/push Build is failing
2022-01-20 12:18:47 -08:00
a5b78384f5
build works, c_allocator no longer required 2022-01-12 09:18:16 -08:00