DEV Community: Eldad Assis

List Artifactory pro admin users - one liner

Eldad Assis — Sat, 25 Apr 2020 09:11:51 +0000

When you have many users in Artifactory, you can get all admins with a quick one liner using the REST API from Linux command line.

for name in \
  $(curl -s -uadmin:password https://host/artifactory/api/security/users | jq ".[].name" | tr -d '"'); do \
  echo \
  "$name: $(curl -s -uadmin:password https://host/artifactory/api/security/users/$name | jq '.admin')"; \
done

Easy!

Open a command prompt in a Kubernetes cluster

Eldad Assis — Mon, 09 Mar 2020 13:06:03 +0000

For cases where I need to open a command prompt in a running container in my Kubernetes cluster, I simply run the following

# Ubuntu
kubectl run my-ubuntu --rm -i -t --image ubuntu:18.04 -- bash

# CentOS
kubectl run my-centos --rm -i -t --image centos:8 -- bash

# Alpine
kubectl run my-alpine --rm -i -t --image alpine:3.10 -- sh

This starts up a pod (in the default namespace by default) and opens a command line in the given container.
As I'm running as root, I can install anything I need for debugging and testing right in my cluster.

Get http code with wget

Eldad Assis — Mon, 09 Mar 2020 12:48:56 +0000

Sometimes I don't have curl available for me in a given environment. Some distributions don't provide it with the default installed utilities and I might not have the privileges to install it.
In such cases, I use wget, which is usually installed.

wget --spider -S -T 2 www.jfrog.org 2>&1 | grep "^  HTTP/" | awk '{print $2}' | tail -1

Run wget --help to see details about the parameters I use here.

The JFrog Platform - The New File System Layout

Eldad Assis — Thu, 27 Feb 2020 10:17:18 +0000

What

In the new JFrog DevOps Platform, we changed all of our products to use a common file system layout, and a single system configuration file.

We defined a few important requirements for this change to take place:

Clear separation of immutable application files and configurations from mutable configuration, data and logs
Intuitive structure that will be easy to navigate and understand its context
Easier customizations for customers who use multiple mounts for various needs (like logs, data and configuration files)
A single system configuration file for the product and its services

Why

We applied various best practice principles along with customer feedback, to meet multiple product needs:

Clear separation of immutable application files (binaries, scripts, tools and internal configurations) from mutable data and configuration files (data, configuration and logs)
Easy management of configuration as code using modern configuration management tools
Similar installation and configuration UX between different JFrog products
Easy navigation and intuitive context

How

We aligned all products to use a similar file system layout.

The new file system layout provides a clear separation of immutable application files (JFROG_HOME/<product>/app) from mutable data, logs and configuration files (JFROG_HOME/<product>/var).

When you install a product, the layout follows the pattern shown in the table below. It has a clear and intuitive structure.

JFROG_HOME
  └── <product>
     ├── app
     │   ├── bin
     │   ├── run
     │   ├── doc
     │   ├── third-party
     │   │   ├── java
     │   │   ├── yq
     │   │   └── others
     │   ├── <service>
     │   │   ├── bin
     │   │   └── lib
     │   └── misc
     │
     └── var
         ├── backup
         │   └── <service>
         ├── bootstrap
         │   └── <service>
         ├── data
         │   └── <service>
         ├── etc
         │   ├── system.yaml
         │   ├── <service>
         │   └── security
         │        ├──master.key
         │        └──join.key
         ├── log
         │   ├── <service logs>
         │   └── archived
         │    └── <archived service logs>
         └── work
             └── <service>

See more details in our Wiki.

Some notes

In Linux based installations (RPM, Deb and Docker)
- JFROG_HOME=/opt/jfrog
- $JFROG_HOME/<product>/var is a symlink to /var/opt/jfrog/<product>
- To customize the location of the mutable directory:
  - Set the JF_PRODUCT_VAR environment variable before running the installation
  - Mount whole the JFROG_HOME/<product>/var on a dedicated persistent storage
  - Using soft links in JFROG_HOME/<product>/var, the user can further customize the final location of mutable files (for example, in Artifactory, point the log directory to a dedicated /mnt/jfrog/artifactory/log directory with a simple ln -s /mnt/jfrog/artifactory/log $JFROG_HOME/artifactory/var/log one time command as part of the initial setup)

The system.yaml

Another important change we introduced is a single, YAML-formatted file for managing the application's system configuration (not to be confused with application configuration).

The system.yaml, which is located in JFROG_HOME/<product>/var/etc, holds the system configuration for your product and its services system configuration.

For example

Database connection details
Configuration of join key
Service ports
Log configurations
Many more...

You can also find a system.full-template.yaml file in the same directory with all supported configuration keys and their default values.

Take extra care when changing configuration values.

You can find more detailed information about this file in our Wiki.

Your private, free Kubernetes registry

Eldad Assis — Mon, 25 Nov 2019 09:32:26 +0000

Working on Kubernetes? Deploying your applications with Helm?
If so, you need a private, trusted and secure Helm repository and Docker registry to get your applications from. And even better if you can have them running inside your Kubernetes cluster!

Great news - JFrog just released a free Container Registry (powered by JFrog Artifactory) that can store and manage your Helm Charts and Docker images. And you can install it anywhere or get it as a service on one of the big cloud vendors (GCP, AWS or Azure).

Get some details in https://jfrog.com/container-registry/

For running it in you Kubernetes cluster, the best way is to use the official Helm chart. See https://hub.helm.sh/charts/jfrog/artifactory-jcr

Simple as

helm repo add jfrog https://charts.jfrog.io

helm install --name jfrog-container-registry jfrog/artifactory-jcr

Done!