Running 2.9.1 (yes, I know, it's old). We have several different clusters, but don't have the same k8s deployments in each cluster. Tried to use a generic policy definition. When it is applied in a cluster which doesn't have one of the deployments, seal doesn't handle the 404 from k8s and dies. Yes, we can change the policies, but also seal shouldn't die in this scenario.
While this was wit
A gui for ssh-copy-id maybe?
and as the tittle says, support for ed25519 keys, maybe a dropdown menu that lets you choose the ehh... cipher is it? for generating a new one. Or at least the ability to connect using them.
I'm in the app folder.
I mkdir exports to make an export folder.
I run rake evm:export:service_dialogs -- --directory exports
I get back:
(in /var/www/miq/vmdb)
Error: argument --directory Destination directory must exist.
Try --help for help.
How can this be? I can ls and see my exports folder in this directory.
Use heptio/workgroup to improve handling of the multiple goroutines that are spawned in each of the discoverers. This will also help us to bubble up errors to main, and handle them appropriately.
An example of this is #224. We wanted to handle the case where re-auth failed 3 times, but there was no good way of bubbling up the error to main.go. We could make reconciler.Run return an error to bub
Describe the bug
When tk8 is run in a directory which does not have config.yaml, it tries to auto generate it by saying:
No default config was provided. Generating one for you.
The auto-generated config.yaml is only usable for aws provisioner and not for others.
To Reproduce
Steps to reproduce the behavior:
tk8 binary in empty folder.Add a description, image, and links to the openstack topic page so that developers can more easily learn about it.
To associate your repository with the openstack topic, visit your repo's landing page and select "manage topics."
We already have some scripts in the
scriptsdirectory. It would be good to run them for every PR.This is also a great task for beginners.