Skip to main content

vertx command line parameters

How to pass command line parameters to "vertx run"

Context

I'm using continuous delivery and need to checkout a git branch then launch the verticle with a parameter.
For example:
  1. I chekcout the "demo" git branch
  2. I deploy it to the target
  3. I remotely run the verticle with "vertx run 'demo'" (this actually doesn't work, but it illustrates my needs)

The solution: use system environment variables

The documentation https://vertx.io/docs/vertx-config/java/ is mentionning it, but it was not straight to me, so here is precisely how I did:

package org.rktmb.vertx
// ...
import io.vertx.config.ConfigStoreOptions;
import io.vertx.config.ConfigRetriever;
import io.vertx.config.ConfigRetrieverOptions;
// ...

public class MainVerticle extends SyncVerticle {
    @Override
    public void start(Future startFuture) throws Exception {
 // ...
        ConfigStoreOptions jsonEnvConfig = new ConfigStoreOptions().setType("env")
            .setConfig(new JsonObject().put("keys", new JsonArray().add("VXBRANCH").add("VXPORT")));
        ConfigRetrieverOptions myOptions = new ConfigRetrieverOptions().addStore(jsonEnvConfig);
        ConfigRetriever myConfigRetriver = ConfigRetriever.create(vertx, myOptions);
        myConfigRetriver.getConfig(asyncResults -> System.out.println(asyncResults.result().encodePrettily()));
 // ..
    }
}
Then, when running the verticle
VXPORT="123" VXBRANCH="prod"  vertx run --classpath=target/test-1.0.0-SNAPSHOT-fat.jar org.rktmb.vertx.MainVerticle
This displays:
{
  "VXBRANCH" : "prod",
  "VXPORT" : 123.0
}

If I ever change the environment variables: the rendered JSON changes accordingly.

Comments

Popular posts from this blog

dockerfile multiline to file

Outputing a multiline string from Dockerfile
I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian.
But I also have a local mirror and would like to use it for packages installation.

Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file.

Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write.
Here you are:

RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 " >>…

npm run build base-href

Using NPM to specify base-href
When building an Angular application, people usually use "ng" and pass arguments to that invocation.
Typically, when wanting to hard code "base-href" in "index.html", one will issue:

ng build --base-href='https://ngx.rktmb.org/foo'


I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin.
I got the habit to build the application with "npm run build" before deploying it.

But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter.

npm run build --base-href='https://ngx.rktmb.org/foo


did not set the base href in indext.html

After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says:
You need to use −− to pass arguments to npm scripts. This did the job!
The command to issue is then:

npm run build -- --base-href='https://ngx.rktmb.org/foo'

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…