davideicardi

import { Bucket } from 'aws-cdk-lib/aws-s3';
import { BucketDeployment, Source } from 'aws-cdk-lib/aws-s3-deployment';
import { CloudFrontWebDistribution, OriginProtocolPolicy } from 'aws-cdk-lib/aws-cloudfront';
import { ARecord, HostedZone, RecordTarget } from 'aws-cdk-lib/aws-route53';
import { CloudFrontTarget } from 'aws-cdk-lib/aws-route53-targets';
import { Construct } from 'constructs';
import { aws_s3 } from 'aws-cdk-lib';

interface StaticWebsiteProps {
  domainName: string;

davideicardi

date --utc --iso-8601=seconds

davideicardi

# Remove all GIT branches starting with `fix/`, just locally
git branch | grep fix/ | xargs -I '{}' git branch -d '{}'

davideicardi

#!/usr/bin/env python3

"""
Based on: https://gist.github.com/ottokruse/1c0f79d51cdaf82a3885f9b532df1ce5
Usage:
 - Save this script somewhere on your path (e.g. `vi /usr/local/bin/aws-console && chmod +x /usr/local/bin/aws-console`)
 - Install dependencies: pip install boto3
 - Make AWS credentials available in one of the usual places where boto3 can find them (~/.aws/credentials, env var, etc.)
 - Excute the script: `AWS_PROFILE=your-profile aws-console`
 - :tada: Your browser opens and you are signed in into the AWS console

davideicardi

# Calculate version that will be incremented for each build whenever Major or Minor change, and different for each branch.
# Solution based on https://k2vacademy.com/2019/04/03/hidden-gems-in-azure-pipelines-creating-your-own-rev-variable-using-counter-expression-in-azure-pipelines/
# This could be useful if gitversion cannot be used.
# Otherwise the best solution is to use instead the default gitversion task: https://github.com/GitTools/actions/blob/main/docs/examples/azure/gitversion/execute/usage-examples.md

# ....

variables:
  # Versioning is handled using a format like major.minor.patch{-snapshot}
  # Major and Minor are fixed, patch is calculated using a counter (it will reset to 0 every time other values change).

davideicardi

# References:
#  https://nodejs.org/en/docs/guides/nodejs-docker-webapp/
#  https://github.com/nodejs/docker-node/blob/main/docs/BestPractices.md
#  https://adambrodziak.pl/dockerfile-good-practices-for-node-and-npm


FROM node:16.13-alpine3.12 AS builder

WORKDIR /usr/src/app

davideicardi

#!/bin/bash

# set -e = exit in case of errors
# set -u = no undefined variable
# set -o pipefail = prevent pipeline errors
# more info: https://gist.github.com/usametov/a134115a0fa1157b45ea5d432510d2f6
set -euo pipefail


# TODO Add your script

davideicardi

import scala.concurrent.{ExecutionContext, Future}

object FutureUtils {
  /**
   * Process elements asynchronous one after another.
   * Equivalent to `Future.sequence(elements.map(transform))`
   * but doing the processing sequentially instead of in parallel
   */
  def mapAsyncSequentially[TInput, TResult](elements: Iterable[TInput])
                                (mapFunction: TInput => Future[TResult])

davideicardi

import java.util.Properties

import org.apache.kafka.streams.scala.ImplicitConversions._
import org.apache.kafka.streams.scala._
import org.apache.kafka.streams.scala.kstream._
import org.apache.kafka.streams.{StreamsConfig, Topology}
import Serdes._

class SimpleTopology(
                     val bootstrapServers: String,

davideicardi

Publish

Add the following configuration to your build.sbt:

  // publish to github packages settings
  publishTo := Some("GitHub <GITHUB_OWNER> Apache Maven Packages" at "https://maven.pkg.github.com/<GITHUB_OWNER>/<GITHUB_PROJECT>"),
  publishMavenStyle := true,
  credentials += Credentials(
    "GitHub Package Registry",