2021-01-25_-_non_interactive_docker_container

anonymous@undisclosed.example.com (Anonymous) — Tue, 15 Jun 2021 20:09:42 +0000

2021-01-25 - (non)interactive docker container

you can run docker container to do some non-interactive processing. eg with:

docker run --rm myalgo:4.2 --foo --bar

when you need to do it interactively, you just add -it:

docker run -it --rm myalgo:4.2 --foo --bar

so far, so good. now how about CI scripts, that on CI server are being run in a non-interactive way, but you also want the very same scripts to be runnable interactively by developers (so that they can eg. ^C it during the run)? it turns out it is fairly simple with tty command to detect if terminal is interactive or not and bash arrays to pass parameters to docker:

EXTRA_FLAGS=()
if tty -s
then
  EXTRA_FLAGS+=("-it")
fi
 
docker run \
  "${EXTRA_FLAGS[@]}" \
  --rm \
  myalgo:4.2 --foo --bar

as a free bonus you can now add multiple optional flags, to the same array and/or use it for all the arguments, to simplify the invocation of docker.

2021-01-25_-_the_flask_path

anonymous@undisclosed.example.com (Anonymous) — Tue, 15 Jun 2021 20:09:42 +0000

2021-01-25 - the flask path

every now and then i use Flask to get some REST service up and running in no time. recently i had an interesting case, as API i exposed was in a form /api/1/branch/<brn>/stuff, where brn was a VCS branch name, that the API referred to. after some time, one of the project teams started to send out their branches data. branches however were in the form feature/foo-bar… and boom – API returned an error, that path does not exist. so the obvious solution was to URL-encode it, i.e. feature%2Ffoo-bar… and the same! it turned out that Flask is kind enough to parse URL-encoded data for you. convenient. unless it is not sth that you want… :/

the answer is “parameter types”. when you normally type in route in flask, it looks like this:

@app.route("/api/1/branch/<brn>/stuff")
def handle_stuff(brn):
    foobar(brn)

you are implicitly getting string parameter type. this is where (and why) Flask URL-decides %2F into /.

there are however other types, like int and path. in particular path can handle %2F properly. so the “correct” code is:

@app.route("/api/1/branch/<path:brn>/stuff")
def handle_stuff(brn):
    foobar(brn)

now users can send out feature%2Ffoo-bar and a proper function will get called, with brn set to feature/foo-bar, as expected.

it took me a bit of searching. the main problem was that i was looking for ways to “disable URL-encoding in flask” (and similar) and there i got bunch of “can't do”, “won't work” and rally nasty hacks in the implementation of a backend. in the end, the solution turned out to be trivial… once you know what are you looking for. it would be nice if it was more explicit in a documentation (FAQ maybe?).

BaSzErr - blog:2021:01:25

2021-01-25_-_non_interactive_docker_container

2021-01-25 - (non)interactive docker container

2021-01-25_-_the_flask_path

2021-01-25 - the flask path