isle/tests/cases/nebula/01-create-cert.sh

# shellcheck source=../../utils/with-1-data-1-empty-node-network.sh
source "$UTILS"/with-1-data-1-empty-node-network.sh

nebula-cert keygen -out-key /dev/null -out-pub pubkey
cat pubkey

(
    isle nebula create-cert \
        --hostname non-esiste \
        --public-key-path pubkey \
        2>&1 || true \
) | grep '\[1002\] Host not found'

isle nebula create-cert \
    --hostname primus \
    --public-key-path pubkey \
    | grep -- '-----BEGIN NEBULA CERTIFICATE-----'
Move create-nebula-cert into nebula create-cert, move most logic into daemon 2024-07-13 14:08:13 +00:00			`# shellcheck source=../../utils/with-1-data-1-empty-node-network.sh`
			`source "$UTILS"/with-1-data-1-empty-node-network.sh`

			`nebula-cert keygen -out-key /dev/null -out-pub pubkey`
			`cat pubkey`

			`(`
			`isle nebula create-cert \`
			`--hostname non-esiste \`
			`--public-key-path pubkey \`
			`2>&1 \|\| true \`
Separate Daemon and Network logic into separate packages In a world where the daemon can manage more than one network, the Daemon is really responsible only for knowing which networks are currently joined, creating/joining/leaving networks, and routing incoming RPC requests to the correct network handler as needed. The new network package, with its Network interface, inherits most of the logic that Daemon used to have, leaving Daemon only the parts needed for the functionality just described. There's a lot of cleanup done here in order to really nail down the separation of concerns between the two, especially around directory creation. 2024-09-09 14:34:00 +00:00			`) \| grep '\[1002\] Host not found'`
Move create-nebula-cert into nebula create-cert, move most logic into daemon 2024-07-13 14:08:13 +00:00
			`isle nebula create-cert \`
			`--hostname primus \`
			`--public-key-path pubkey \`
			`\| grep -- '-----BEGIN NEBULA CERTIFICATE-----'`