httpie | httpie running in docker alpine | Continuous Deployment library

The B3MultiFormat propagator doesn't consider the parent span id field while serialising the context into HTTP headers since X-B3-ParentSpanId is an optional header https://github.com/openzipkin/b3-propagation#multiple-headers. You can expect the X-B3-TraceId and X-B3-SpanId to be always present but not the remaining ones.

Edit:

Are you setting the concrete tracer provider? It doesn't look like from the shared snippet but I don't know if you are actual application code. It's all no-op if you do not set the sdk tracer provider i.e no recording spans are created in FastAPI service. Please do the following.

Perhaps this is the solution:

Assuming the input is valid JSON, the following jq program will yield an array of the distinct names:

In your case the command looks like this:

To summarize the comments:

It's currently not possible to do that with Fargate. More details here.

Nevertheless there are two other options that could work:

1. Deploy the containers on EC2 instead of Fargate, because there you use different Network Modes than only awsvpc and can configure the port mapping.
2. Deploy container via AWS App Runner where you can as well pause the services when you don't need them so that it's a low budget option as well and you don't need to take care of anything except for creating the App Runner service. The downside is that the creation of the App Runner service is currently only possible via CLI or UI but not yet via CloudFormation.

Without knowing your OS and its version, it will be a guess answer :)

I bet you are running an old Fedora version or CentOS?

If that's the case, the HTTPie version is very old (0.9.4), and at that time it was bundled using Python 2. So when you do sudo yum install httpie it will install http and https executable as Python 2 modules.

One solution that was proposed in comments is to use python3 -m pip install --upgrade httpie: it will make sure you are installing HTTPie for Python 3. And http & https executable will be available too. If you do so, you must first remove the HTTPie version you installed via yum.

Please enable the quarkus-smallrye-jwt TRACE logging to see why the tokens are rejected. And indeed, as you have also found out, https protocol needs to be enabled in the native image, which can be done, as you have shown :-), by adding --enable-url-protocols=https to the native profile's properties in pom.xml.

This PR will ensure adding it manually won't be required.

thanks

Windows shell quoting rules are different, so you can't use :='' with single quotes as all the osx/linux examples do, you need double quotes.

The error message that you get says "Expecting property name enclosed in double quotes", but thats confusing since it is in double quotes to the naked eye.

Escaping the the double quotes inside the json literal will do this. You do this by doubling up the quote character, as "".

"city" => ""city""

If you want to create a hmac for the post request and set it to the header, simply use cryptoJs as below in the pre-request script.