hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 09:22:43 +03:00
Code Issues Projects Releases Wiki Activity
1130e271c7
graphql-engine/v3/dev-auth-webhook.Dockerfile

21 lines
407 B
Docker
Raw Normal View History

Inject trace context headers into requests to the auth hook. (#458) This injects trace context headers into requests to the auth hook, allowing us to figure out how much time is spent here. I added a basic tracing setup to the dev-auth-webhook, using `tracing-util`, allowing me to verify that this works. This required moving the Dockerfile to the root so the context contains the `tracing-util` crate too. I have also fixed the reference agent (by updating it), and patched our Docker Compose files to correctly set up connectivity to Jaeger. V3_GIT_ORIGIN_REV_ID: 2ff930bda4147d00dcc73268a814b08c8a07a359
2024-04-11 10:41:06 +03:00
# build
FROM rust:1.77 AS builder
WORKDIR /app
COPY ./Cargo.toml ./Cargo.toml
Fix `dev-auth-webhook` Docker image, build all in CI (#535) <!-- Thank you for submitting this PR! :) --> ## Description I think this broke when moving folders around, realised we weren't even building it other than in `main`, this rectifies that. V3_GIT_ORIGIN_REV_ID: f822290f9a00159d4b1b55553f31175b697a16c1
2024-05-01 12:53:30 +03:00
COPY ./crates ./crates
Inject trace context headers into requests to the auth hook. (#458) This injects trace context headers into requests to the auth hook, allowing us to figure out how much time is spent here. I added a basic tracing setup to the dev-auth-webhook, using `tracing-util`, allowing me to verify that this works. This required moving the Dockerfile to the root so the context contains the `tracing-util` crate too. I have also fixed the reference agent (by updating it), and patched our Docker Compose files to correctly set up connectivity to Jaeger. V3_GIT_ORIGIN_REV_ID: 2ff930bda4147d00dcc73268a814b08c8a07a359
2024-04-11 10:41:06 +03:00
Fix `dev-auth-webhook` Docker image, build all in CI (#535) <!-- Thank you for submitting this PR! :) --> ## Description I think this broke when moving folders around, realised we weren't even building it other than in `main`, this rectifies that. V3_GIT_ORIGIN_REV_ID: f822290f9a00159d4b1b55553f31175b697a16c1
2024-05-01 12:53:30 +03:00
WORKDIR /app/crates/auth/dev-auth-webhook
Include the dev-auth-webhook crate in the workspace. (#500) Now that the Dockerfile is in the root, there's no reason not to. V3_GIT_ORIGIN_REV_ID: 62199715c2a5aaaf1ac45e22c9d8bdac6838fd72
2024-04-24 11:11:48 +03:00
RUN cargo build --release --package=dev-auth-webhook
Inject trace context headers into requests to the auth hook. (#458) This injects trace context headers into requests to the auth hook, allowing us to figure out how much time is spent here. I added a basic tracing setup to the dev-auth-webhook, using `tracing-util`, allowing me to verify that this works. This required moving the Dockerfile to the root so the context contains the `tracing-util` crate too. I have also fixed the reference agent (by updating it), and patched our Docker Compose files to correctly set up connectivity to Jaeger. V3_GIT_ORIGIN_REV_ID: 2ff930bda4147d00dcc73268a814b08c8a07a359
2024-04-11 10:41:06 +03:00
# copy
FROM debian:bookworm-slim
Include the dev-auth-webhook crate in the workspace. (#500) Now that the Dockerfile is in the root, there's no reason not to. V3_GIT_ORIGIN_REV_ID: 62199715c2a5aaaf1ac45e22c9d8bdac6838fd72
2024-04-24 11:11:48 +03:00
COPY --from=builder /app/target/release/dev-auth-webhook /usr/bin
Inject trace context headers into requests to the auth hook. (#458) This injects trace context headers into requests to the auth hook, allowing us to figure out how much time is spent here. I added a basic tracing setup to the dev-auth-webhook, using `tracing-util`, allowing me to verify that this works. This required moving the Dockerfile to the root so the context contains the `tracing-util` crate too. I have also fixed the reference agent (by updating it), and patched our Docker Compose files to correctly set up connectivity to Jaeger. V3_GIT_ORIGIN_REV_ID: 2ff930bda4147d00dcc73268a814b08c8a07a359
2024-04-11 10:41:06 +03:00
support OpenTelemetry zipkin propagator (#466) Support both W3C and Zipkin B3 headers and connectors will prefer B3 headers to extract traces because Cloud Run doesn't respect those headers. V3_GIT_ORIGIN_REV_ID: 1471b848e71d87420bc75b9adee60951f306c856
2024-04-16 17:55:54 +03:00
RUN apt-get update && \
apt-get install -y openssl
Inject trace context headers into requests to the auth hook. (#458) This injects trace context headers into requests to the auth hook, allowing us to figure out how much time is spent here. I added a basic tracing setup to the dev-auth-webhook, using `tracing-util`, allowing me to verify that this works. This required moving the Dockerfile to the root so the context contains the `tracing-util` crate too. I have also fixed the reference agent (by updating it), and patched our Docker Compose files to correctly set up connectivity to Jaeger. V3_GIT_ORIGIN_REV_ID: 2ff930bda4147d00dcc73268a814b08c8a07a359
2024-04-11 10:41:06 +03:00
EXPOSE 3050
Include the dev-auth-webhook crate in the workspace. (#500) Now that the Dockerfile is in the root, there's no reason not to. V3_GIT_ORIGIN_REV_ID: 62199715c2a5aaaf1ac45e22c9d8bdac6838fd72
2024-04-24 11:11:48 +03:00
ENTRYPOINT ["/usr/bin/dev-auth-webhook"]
Reference in New Issue Copy Permalink