Using: https://github.com/GoogleContainerTools/container-structure-test
Install:
$ brew install container-structure-test
Run it with the nonroot.yaml
config file provided in the gist:
Using: https://github.com/GoogleContainerTools/container-structure-test
Install:
$ brew install container-structure-test
Run it with the nonroot.yaml
config file provided in the gist:
package main | |
import ( | |
"fmt" | |
"log" | |
"net/http" | |
"github.com/go-chi/chi/v5" | |
"github.com/go-chi/chi/v5/middleware" | |
) |
package gingko_subtests_test | |
import ( | |
"testing" | |
"github.com/stretchr/testify/assert" | |
) | |
func TestCheckingBooksOutOfLibrary(t *testing.T) { | |
t.Run("when the library has the book in question", func(t *t.Testing) { | |
t.Run("if the book is available, it lends it to the reader", func(t *t.Testing) { |
package main | |
import ( | |
"fmt" | |
"log" | |
"sync" | |
) | |
type Input struct { | |
Id string |
package main | |
import ( | |
"context" | |
"fmt" | |
"sync" | |
"time" | |
) | |
// simply runs a program to showcase how to properly leverage |
package main | |
import ( | |
"io" | |
"io/ioutil" | |
"log" | |
"net" | |
"net/http" | |
"golang.org/x/crypto/ssh" |
Notes from watching The Many Meanings of Event-Driven Architecture - Martin Fowler -GOTO 2017
This post also covers it: https://martinfowler.com/articles/201701-event-driven.html
If System A needs to communicate with System B, i.e. a customer management system needs to tell a quoting system to trigger a requote, then if it's via API A needs to know B's API, etc.
-- This is simply an example of how to get child records as JSON. | |
-- | |
SELECT ii.id AS invoice_id, | |
JSON_PRETTY(JSON_OBJECT('items', | |
( | |
SELECT | |
CAST(CONCAT('[', | |
GROUP_CONCAT(JSON_OBJECT( | |
'id', li.id, | |
'name', li.name, |
# Sources: | |
# https://gist.github.com/zchee/9c78f91cc5ad771c1f5d | |
# https://github.com/JetBrains/ideavim | |
let mapleader=";" | |
nnoremap <Leader>nc :e ~/.ideavimrc<CR> | |
nnoremap <Leader>nr :action IdeaVim.ReloadVimRc.reload<CR> | |
nnoremap <Leader>q :q<CR> |
Talk: https://www.youtube.com/watch?v=pspy1H6A3FM
Def: An architectural style defined by the constraints Client-Server, Stateless Communications, Cachin, Uniform Interface, Layered System and (optionally) Code-on-demand.
Rest is perfectly defined. There is a set of rules that define it. If you follow them, it's REST, if not, then it's not.