- Vault v1.9.3
- Consul v1.11.2
- Update expired TLS certificates (thanks @daveyb)
- Prefer local container data storage for Vault and Consul
- Update documentation
- Vault v1.9.0, v1.9.1, and v1.9.2
- Consul v1.11.1
- Update documentation
- Vault v1.8.3
- Consul v1.10.3
- Update documentation
- Vault v1.8.2
- Consul v1.10.2
- Update documentation
- Vault v1.8.1
- Vault v1.8.0
- Consul v1.10.1
- Update documentation
- Vault v1.7.3
- Consul v1.9.7
- Update documentation
- Vault v1.7.2
- Update documentation
- Vault v1.7.1
- Update documentation
- Require Terraform >= 0.15.0
- Update documentation
- Update form script
- Update documentation example
- Vault v1.7.0
- Consul v1.9.4
- Update documentation
- Update Docker provider
- Vault v1.6.2
- Consul v1.9.2
- Update documentation
- Vault v1.6.1
- Update for Terraform v0.14 compatibility
- Clean up .terraform.lock.hcl files in unform
- Script message improvements
- Vault v1.6.0
- Consul v1.9.0
- Switch to kreuzwerker/docker
- Update documentation
- Vault v1.5.4
- Consul v1.8.4
- Update documentation
- Vault v1.5.3
- Fix form script
- Remove deprecated use_vault_oss configuration
- Update documentation
- Upgrade for Terraform 0.13 compatibility
- Simplified required environment variable configuration for flavors & counts
- Add vault_disable_mlock configuration
- Default is true for integrated storage (raft flavor)
- Default is false for Consul storage (consul flavor)
- Update documentation
- Vault v1.5.2
- Consul v1.8.3
- Update scripts
- Update documentation
- Vault v1.5.0
- Consul v1.8.1
- Update scripts
- Update documentation
- Vault v1.4.3
- Katacoda awareness circuit
- Consul v1.8.0
- Configurable DOCKER_HOST TF variable
- Updates scripts
- Update documentation
- Consul v1.7.4
- Update documentation
- Vault v1.4.2
- Remove Consul DNS as container DNS source
- Update documentation
- Vault v1.4.1
- Update documentation
- Vault v1.4.0
- Introduce flavors
- Reorganize locations for configuration and data
- Consistent use of data volume for Raft and Filesystem storage backends
- Add Vault Integrated Storage (Raft) flavor
- Add Vault Consul Storage flavor
- Update documentation
- Vault v1.3.3
- Update scripts with more helpfulness in error outputs
- Update documentation
- Consul v1.7.0
- Fix Terraform issue with labels
- Update documentation
- Vault v1.3.2
- Consul v1.6.3
- Remove interpolation to prevent warnings (thanks @fprimex)
- Updated documentation
- Vault v1.3.1
- Update documentation
- Vault v1.3.0
- Consul v1.6.2
- Update documentation
- Vault v1.2.4
- Update Yellow Lion / telemetry / dashboard / etc.
- Update Black Lion custom template
- Update Agent guide
- Use 825d TTLs in server TLS material (Hi, Catalina!)
- Update documentation
- Vault v1.2.3
- Consul v1.6.1
- Revert to default system-wide TTL and Maximum TTL values
- Create private network in form/do not manage with TF
- Begin TLS configuration for Grafana and other container friends
- Update documentation
- Vault v1.2.2
- Vault v1.2.1
- Add
SYS_ADMIN
capability to all containers - Update all templates filenames and template filename references
- Update documentation
- Vault v1.2.0
- Consul v1.5.3
- API_ADDR set in config template instead of environment variable
- Add vault_server_log_format and matching TF_VAR for choosing log format
- Update documentation
- Consul v1.5.2
- Add a Vaultron Docker private network to top level Terraform configuration
- Statically assign container IP addresses within vaultron-network
- Add SKIP_CHOWN to Vault container resources
- Update TLS certificates
- Update documentation
- BREAKING CHANGE: Vaultron now requires Terraform v0.12.0+ (thanks @fprimex)
- Update documentation
- Vault v1.1.3
- terraform fmt all the things!
- Set an explicit https VAULT_REDIRECT_ADDR in env
- Update documentation
- Consul v1.5.1
- Update documentation
- Add NET_ADMIN and SYS_PTRACE capabilities to all containers
- Vault v1.1.12
- Consul v1.5.0
- Reissued all certificates and keys
- Add RabbitMQ example
- Renamed CA cert file
- Update unform cleanup tasks
- Update documentation
- Vault v1.1.1
- Consul v1.4.4
- Update TLS certificates
- Update documentation
- Vault version 1.1.0
- Update scripts
- Update documentation
- Consul v1.4.3
- Disable client certs in custom template
- Update documentation
- Fixup scripts
- Update templates for Consul
- Use specific Node IDs in Consul so that ancient versions work again
- Update LDAP auth method examples
- Vault v1.0.3
- Consul v1.4.2
- Updated examples / documentation
- Vault v1.0.2
- Update documentation
- Vault v1.0.1
- Consul configuration cleanup and updates
- Update example / test scripts
- Add workaround to unform for uid 0 owned local Consul data under Linux
- Update documentation
- Vault v1.0.0
- Update Consul ACL token format
- Default log levels
- Vault v0.11.5
- Consul v1.4.0
- Remove enable_script_checks from older Consul templates
- blazing_sword now uses a separate Terraform configuration
- Update documentation
- Vault v0.11.4
- Container namespace
- Reloadable Vault log level
- Update scripts
- Update documentation
- Vault v0.11.3
- Consul v1.3.0
- Use
vaultN
for Consul client node names - Update scripts
- Clean up configuration
- Update documentation
- Vault v0.11.2
- Yellow Lion is now more plug and play; see README for more details
- Vault v0.11.1
- Update configuration for telemetry
- Update documentation
- Vault v0.11.0
- Consul v1.2.2
- Additional DNS container configuration to leverage Consul DNS API
- Add tranistize test script
- Update apprulez test script
- Increase wait to 3 seconds in blazing_sword
- Add an acl_agent_master_token to Consul client & server agent configuration
- Update documentation
- Add Vault Agent example stubs
- Update documentation
- Update CONTRIBUTORS
- Update config path (thanks to feedback from @roooms)
- Vault version 0.10.4
- Consul v1.2.0
- Vault version 0.10.3
- Move to one unseal key in blazing_sword for simplicity
- Update published ports for standby instances
- Upate blazing_sword for published ports updates
- Move plugins folder to vault
- Fix test_vaultron
- Update Documentation
- Vault v0.10.1
- Consul v1.0.7
- Yellow Lion is now opt-in with TF_VAR_vaultron_telemetry_count=1
- Remove example Graphite service and health definitions
- Prefer simplicity over specificity in naming containers
- Remove beta and RC templates
- Correct typo in form script (thanks @greyspectrum)
- Correct typo in ion darts script (thanks @lauradiane)
- Change CHANGELOG sort ordering
- Update documentation
- Vault version 0.10.0
- Yellow Lion appears
- Clean up configuration cruft
- Health check and service definition examples for Yellow Lion container
- Update documentation
- Relax ACL default policy to allow while finalizing configuration
- Document TLS details
- Vault 0.10.0-beta1
- Complete TLS work
- Vault v0.9.6
- ACLs by default
- TLS by default
- Drop custom Consul version bits
- Script improvements
- Vault v0.9.5
- Consul v1.0.6
- Initial CLI capabilities checking added to skydome
- Examples/tests/scripts improvements
- Examples/tests/scripts updates
- Update documentation
- Vault v0.9.3
- Update blazing sword
- Adulted away from delightful emojis for the sake of a bit of UX portability
- Add a Root+Intermediate CA guide for PKI backend
- Update examples
- Update tests
- Update documentation
- Vault v0.9.1
- Added variable
vault_server_log_level
variable for Vault log level - Updated templates
- Updated documentation
- Consul v1.0.2
- Monitoring with Graphite and Grafana guide
- PostgreSQL backend guide
- Updated example scripts
- Updated documentation
- Added more examples
- Renamed functions
- Consul 1.0.1
- Vault 0.9.0
- Consul 1.0.0
- Add initial file backend support
- Add initial Vault plugin support
- Custom TLS and TLS with file backend templates
- Update scripts
- Add more examples
- Vault version 0.8.3
- Update Consul to version 0.9.3
- Update Vault to version 0.8.2
- Explicitly opt out of Consul ACLs with acl_enforce_version_8 set to false in Consul versions >= 0.8.0
- Consul v0.9.2
- Implement
VAULT_CLUSTER_INTERFACE
from the default entrypoint script - Explicitly set Raft protocol 3 in >= 0.8.x templates
- Improve form script
- Update documentation
- Update test_vaultron
- Reintroduce count on Consul clients (needs refinement)
- Correct Vault custom template configuration
- Terraform apply, init, and plan failures now show most recent output
- Fix test default var value
- Update documentation
- Fix for Consul server with count issue
- Vault version 0.8.0!
- Reduced resource usage via count pattern in Vault module (thanks @fprimex)
- Update indexes in naming for count usage
- Fix unform script
- Even more blazing from Blazing Sword!
- TF count rebase (thanks @fprimex)
- Custom Vault binary support!
- Add support for Vault version 0.8.0-rc1
- Update and reflow on the README (shoutout to @angrycub for the inspiration!)
- Update example test scripts
- Address SC2181 in form
- Address SC2004 in unform
- Address SC2046 in skydome
- Preserve provider modules for Terraform 0.10.0+
- Add example for MongoDB secret backend
- Flip date and op in log names for easy reading (thanks @fprimex)
- Modularize Terraform configuration and more tests (thanks @fprimex)
- Consistent comment banners in configurations
- Remove TF logs on successful unform run
- Add some miscellaneous test scripts for Vault
- Fix a user message type
- Disable log cleanup (needs more discussion)
- Set
keep_locally
to true (addresses 2 TF errors during unform issue) \o/
- Add error tracking to unform (thanks @fprimex)
- POSIX changes that make dash happy (thanks @fprimex)
- Use terraform console to get config values (thanks @fprimex)
- Start a testing script (thanks @fprimex)
- Verified working in both Linux and Docker for Mac environments
- Log Terraform operations, store and use plan (thanks @fprimex)
- Move common things to Skydome, fixes to state handling (thanks @fprimex)
- Check for Terraform (fixes #6) and better Terraform output (thanks @fprimex)
- Set variables and ignore logs (thanks @fprimex)
- Update documentation
- Disable script checks in 0.9.0 configurations
- Spruce up scripts
- Add execute versus source checking to form script (thanks @fprimex)
- Drop to executing form instead of sourcing and prompt user to set env vars
- Add examples directory and initial Vault PKI policy example
- Add CONTRIBUTING.md
- Add CONTRIBUTORS.md
- Reduce range of acceptable Consul versions to those actually published to DockerHub (0.7.0-CURRENT)
- Remove templates for invalid Consul versions
- Update documentation
- Update OSS server common configuration template
- Move common configuration from entry point to templates
- Update form script
- Update Consul client configuration to match architectural diagram
- Improve form error output
- Switch from notion of "extra configuration" to "common configuration"
- Create server common configuration
- Add initial version-specific common configuration template stubs
- Have fun with "Technical Specifications" (remember the roots!)
- Add support for supported Vault docker image versions (0.6.1-CURRENT)
- Add support for supported Consul docker image versions (0.6.0-CURRENT)
- Update documentation
- Expose DNS from Consul server one to host Mac (tcp/udp 8600)
- Tidy up Terraform configuration
- Use consistent naming for Consul and Vault instances throughout
- Enable intial support for Consul and Vault version-specific configuration
- Use Consul servers for DNS
- Enable script checks
- Update documentation
- Update ignores
- HA mode confirmed working
- Update documentation
- Three Consul client agents
- Three Vault servers
- Provide audit logs directory mapping
- Enable file based audit logging on initially active server
- Update scripts
- Update documentation
- Cluster is now using Consul client agents to which Vault servers connect
- Stubbed a pre-0.7.x config file so that 0.6.x versions can be run soon
- Reworked naming to distinguish clients and servers
- Update documentation
- Keep with Voltron theme by renaming
vault_kitchen_sink
toblazing_sword
- Update documentation
- Removed Makefile and switched to direct script sourcing/executing
- Why so blue, vault_kitchen_sink?
- Updated README
- Add sad hack to disable registration since we have Vault talking to Consul server directly and health checks don't always work that way
- Configuration cleanup
- Variable translation fix for disable_clustering
- Initial release
- One Vault server
- Three Consul servers