tboeghk

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<profiles version="12">
<profile kind="CodeFormatterProfile" name="Shopping24 GmbH" version="12">
<setting id="org.eclipse.jdt.core.formatter.comment.insert_new_line_before_root_tags" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.disabling_tag" value="@formatter:off"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_annotation" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_before_comma_in_type_parameters" value="do not insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_before_opening_brace_in_type_declaration" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_type_arguments" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.brace_position_for_anonymous_type_declaration" value="end_of_line"/>

tboeghk

80470 => 80470
ABC => ABC
ABM => ABM
ACL => ACL
ACPI => ACPI
ADAC => ADAC
ADSL => ADSL
AEG => AEG
AG => AG
AGP => AGP

tboeghk

varnishd -C -f /etc/varnish/main.vcl

tboeghk

# download
wget http://repo.or.cz/w/wortliste.git/blob_plain/master:/wortliste

# easy things
awk -F ';' '{print $1;}' > list_words_dictionary.de.txt

# ok, complex
grep -v ";-2-;" wortliste |awk -F ';' '{print $2;}' | tr -d "[·|-<>]" | grep "=" | awk -F '=' '{print $1"\n"$2"\n"$3"\n"$4;}' | sort -u | tr [:upper:] [:lower:] >> list_words_dictionary.de.txt

# reset

tboeghk

Route53Cleanup

Report on Route53 IP records not found in the EC2 running instances.

usage: route53-cleanup.py --zoneid A2BCD3FGH4ZXYO  

Route53 Cleanup Reporter  

tboeghk

These Kubernetes resources deploy a recent Graylog2 cluster on Kubernetes in #yolo mode without any persistence – The ideal way to quickly run, inspect and adapt a Graylog cluster in Kubernetes. The Deployment will install:

• Graylog 2.4.0
• Elasticsearch 5.6.3
• Kibana 5.6.3

Deploy Graylog

tboeghk

{"lastUpload":"2021-05-31T11:41:23.468Z","extensionVersion":"v3.4.3"}

tboeghk

💡 SOLR-11904 demonstration

I set up this small Gist to help demonstrate an edge case when running Solr as a TLOG/PULL replica ensemble with authentication enabled and authorization being rather strict.

• Issue in Solr issue tracker
• Pull Request

The problem is that in said environment, the PULL replica cannot check the TLOG leader replicas for updates. It get's rejected with a 401 HTTP error code.

tboeghk

💡 SOLR-15437 demonstration

I set up this small Gist to demonstrate a possible bug in Solr's Re-ranking / LTR / QueryComponent.

• Issue in Solr Jira

When combining Re-Ranking and Sorting in a query in a Solr Cloud environment on a collection with multiple shards, the result is sorted randomly.

Reproducing the error

tboeghk

name: terraform state drift detection

# Execute this action on push to main and everyday at 7am
on:
  push:
    branches:
      - main
  workflow_dispatch:
  schedule:
    - cron:  '0 7 * * *'