node-client | js client-side implementation | Runtime Evironment library

Kafka Confluent Control Centre is not available as free . Trial version is available for one month. There is other product called lenses , you can also check that.

When you first connect to a kafka node, it will give you back all the kafka node and the url where to connect. Then your application will try to connect to every kafka directly.

Issue is always what is the kafka will give you as url ? It's why there is the KAFKA_ADVERTISED_LISTENERS which will be used by kafka to tell the world how it can be accessed.

Now for your use-case, there is multiple small stuff to think about:

Let say you set plaintext://kafka:9092

• This is OK if you have an application in your docker compose that use kafka. This application will get from kafka the URL with kafka that is resolvable through the docker network.
• If you try to connect from your main system or from another container which is not in the same docker network this will fail, as the kafka name cannot be resolved.

==> To fix this, you need to have a specific DNS server like a service discovery one, but it is big trouble for small stuff. Or you set manually the kafka name to the container ip in each /etc/hosts

If you set plaintext://localhost:9092

• This will be ok on your system if you have a port mapping ( -p 9092:9092 when launching kafka)
• This will fail if you test from an application on a container (same docker network or not) (localhost is the container itself not the kafka one)

==> If you have this and wish to use a kafka client in another container, one way to fix this is to share the network for both container (same ip)

Last option : set an IP in the name: plaintext://x.y.z.a:9092

This will be ok for everybody... BUT how can you get the x.y.z.a name ?

The only way is to hardcode this ip when you launch the container: docker run .... --net confluent --ip 10.x.y.z .... Note that you need to adapt the ip to one valid ip in the confluent subnet.

If you are using User Application then you need to check Authorization Code Grant to learn how DocuSign using this type of Grant to generate AccessToken and RefreshToken.

In User Application flow, AccessToken is provided for 8 hours and once AccessToken expires then your App needs to use Refresh Token to generate new set of Access and Refresh Token.

But if you are using System Integration then you need to check JSON Web Token Grant to learn how DocuSign provides AccessToken using JWT.

In System Integration flow, it is assumed that an API user in your App behind the scene will call DS API, and there is no DocuSign User interaction to login after certain interval to provide access to your App to generate Access token on behalf of the logged in user once Refresh token expires. System Integration Flow will get one time consent, Obtaining Consent explains how to get Consent. Once consent in provided to the Integrator Key then Integrator Key via your app can generate AccessToken any time, and this AccessToken will be valid for 3600 seconds, once it expires then you create new JWT and call DocuSign OAUTH API to generate new AccessToken for next 3600 seconds.

Node JS_03 is an example showing how User Application flow works.

Node JS_01, check for dsJwtAuth.js is an example showing how System Integration flow works using JWT.

Most libraries allow you to add custom parameters that isn't supported by the library itself. Sometimes it's documented, sometimes you have to read through the source to find it.

For your first example you can use:

Finally it solved by copy and pasting .graphql files inside the build/apollo by this command

We want to control the kafka docker container configuration - /etc/kafka/server.properties outside from the container

I would avoid mounting a server.properties file from the host since every setting within the container can be configured by environment variables like KAFKA_(variable) - https://docs.confluent.io/current/installation/docker/config-reference.html#confluent-kafka-configuration

Rather, you can use env_file for the compose file and move all your variables there

First you would mount the disk to a directory in /etc/fstab on the linux host, then use volumes - https://docs.docker.com/compose/compose-file/#volumes

Found my own issue. The autoCommit configuration was correct, as evidenced by the logs. The issue was by default the parameter in the block was set to true, so it was not fetching the latest values of the fields. Setting to false forces the application to re-read the value of the field.

Quote from official documentation:

With the default registry (registry.npmjs.org), unpublish is only allowed with versions published in the last 72 hours. If you are trying to unpublish a version published longer ago than that, contact support@npmjs.com.

Link - https://docs.npmjs.com/cli/unpublish