loncarales

{
  "basics": {
    "name": "Ales Loncar",
    "image": "https://resume.loncar.net/picture.png",
    "label": "Senior Cloud & DevOps Engineer | Automation Specialist",
    "summary": "Accomplished freelance Cloud and DevOps Engineer with 20+ years of experience delivering production-grade, cloud-native, containerized, and automated solutions. Specializes in infrastructure as code, CI/CD pipelines, platform engineering, and DevSecOps practices to streamline deployment, enhance security, and improve developer experience. Combines a software engineering mindset with deep DevOps expertise to architect and implement scalable, secure, and resilient platforms. Passionate about automation, continuous improvement, and mentoring teams in modern engineering practices.",
    "headline": "Freelance Cloud & DevOps Engineer | Platform Engineer | Kubernetes | CI/CD | DevSecOps",
    "keywords": [
      "Cloud",
      "DevOps",

loncarales

loncarales

---

- name: Verify
  hosts: all

  tasks:
    - name: Gather the package manager facts
      package_facts:
        manager: auto

loncarales

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

loncarales

stage('NPM: Config') {
  withCredentials([usernamePassword(credentialsId: nexusCredentialsId, passwordVariable: 'NEXUS_PASSWORD', usernameVariable: 'NEXUS_USERNAME')]) {
    def token = sh(returnStdout: true, script: "set +x && curl -s -k -H \"Accept: application/json\" -H \"Content-Type:application/json\" -X PUT --data '{\"name\": \"$NEXUS_USERNAME\", \"password\": \"$NEXUS_PASSWORD\"}' https://nexus-repository.net:8088/repository/my-npm/-/user/org.couchdb.user:$NEXUS_USERNAME 2>&1 | grep -Po '(?<=\"token\":\")[^\"]*'")
    sh "set +x && echo \"//nexus-repository.net:8088/repository/my-npm/:_authToken=$token\" >> .npmrc"
  }
}

loncarales

# Upload the package
mvn -s user-settings.xml deploy:deploy-file \
    -Durl=https://artifactory.hostname.com/maven-release \
    -DrepositoryId=central \
    -Dfile="my-package-1.0.0.zip" \
    -DgroupId=com.package.my \
    -DartifactId=my-package \
    -Dversion=1.0.0 \
    -Dpackaging=zip \
    -DgeneratePom=false

loncarales

Getting started

$ pip install ansible-inventory-grapher

# DOT files are stored in ./graphs folder
$ ansible-inventory-grapher -i hosts.ini -d graphs -o loncar_net.dot --visible-vars=ansible_host --visible-vars=ansible_user loncar_net

# The resulting graphs can then be converted to pngs using this command. Assuming the DOT files are stored in graphs folder
$ for f in graphs/*.dot ; do dot -Tpng -o graphs/`basename $f .dot`.png $f; done

loncarales

Analysis

Handling sensitive data

Currently sensitive information, such as passwords, server IP addresses, ... are hard-coded and stored in plain text. If sensitive data must be saved, it must be encrypted first. The best option would be to use a tool for securely managing secrets and encrypting, for example, HashiCorp Vault.

Automation

Artefact building and method of deployment are done manually as described in README.md file. The whole process (configuration, software provisioning and application deployment) can be fully automated. To solve the problem of environment drifting in release pipeline Infrastructure as Code (IaC) approach should be used. Continuous configuration automation (CCA) tools can be thought of as an extension of traditional IaC frameworks. Notable CCA tools: Ansible, SaltStack, Terraform.

loncarales

#!/bin/bash

mkdir git-merge-test
cd git-merge-test
git init
touch merge.txt
git add merge.txt
echo "this is some content to mess with" > merge.txt
git commit -am 'we are commiting the inital content'
git checkout -b new_branch_to_merge_later

loncarales

[user]
    name = user_name
    email = user_email
[apply]
    # Detect whitespace errors when applying a patch
    whitespace = fix
[core]
    editor = nvim
    autocrlf = input
    safecrlf = true