Skip to content

Conversation

@raffenet
Copy link

@raffenet raffenet commented Oct 31, 2025

I'm working thru the create-beehive.sh script to try and stand up an env locally I can develop and modify. This PR will have accumulated fixes for getting this env going from scratch. So far:

  1. Fix paths to yaml configuration files for various services
  2. Fix influxdb setup and wait loop

TODO: fix usage of update-rabbitmq-auth.sh script. The commands and arguments in create-beehive.sh do not match what the script expects. This is now done.

Make sure to capture both stdout and stderr when attempting to start
influxdb. Messages about it already being setup are printing to stderr
in my environment. Also fix a typo match expression "setup"->"set up".
This reverts commits [958b192] and [dca6259]. Namespace support is not
fully baked for instance in the create-beehive.sh script. We can add it
back later when we have it sorted out.
Fix names to reflect the ones created by the current scripts in
waggle-pki-tools.
Plan to use GitHub actions means we need to monitor this directory.
@raffenet raffenet force-pushed the misc-fixes branch 6 times, most recently from ebdb18c to 6e325c8 Compare November 7, 2025 20:19
Test the create-beehive.sh script on a simple k3s cluster.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant