Skip to content

Latest commit

 

History

History
54 lines (41 loc) · 1.61 KB

README.md

File metadata and controls

54 lines (41 loc) · 1.61 KB

Introduction

You have found the installation folder for trcdb templates and secrets.

Prerequisites

This assumes the existence of a vault with tokens. You'll need a root or unrestricted token to initialize data from here on out. If you're a security purist, you'll already have deleted the root token at this point and will just operate with the unrestricted dev token for the steps below.

Generating empty seed files

trcpub -env=dev -token=$VAULT_TOKEN -addr=https://<vaulthost:vaultport>
trcx -env=dev -novault
trcx -env=dev -certs -novault

Edit seed files and provide certificates.

At this point you want to edit all seed variables in preparation for publish. After running trcx -certs, a certs folder will appear under trc_seeds with placeholder empty certificate files. You'll want to replace these placeholder files with the real thing.

Publish initial trcdb seed data

trcinit -env=dev -token=$VAULT_TOKEN -addr=https://<vaulthost:vaultport> -indexed=TrcVault
trcinit -env=dev -certs -token=$VAULT_TOKEN -addr=https://<vaulthost:vaultport>

TrcDb installation

From the root of the tierceron project, run the following commands.

cd atrium
make devplugintrcdb
cd ../installation/trcshhive/trcsh-curator/deploy
./deploy.sh (for trc-vault-plugin)

TrcDb refresh Vault Database access restrictions

Access to trcdb is ip controlled via cidr block using the seed k/v cidrblock.

trcx -env=dev -token=$VAULT_TOKEN -restricted=VaultDatabase -serviceFilter=config -indexFilter=config
trcinit -env=dev -token=$VAULT_TOKEN  -addr=$VAULT_ADDR -restricted=VaultDatabase