Gabriel Adrian Samfira 05057e37fd Start pool managers in the background ... Garm no longer fails on startup if a pool manager cannot be started. It will attempt to start the pool manager in the background. If it fails due to an unauthorized error, it will sleep for 3 hours. It is unlikely it will work a second time if credentials are not updated in the config and garm is restarted, so no point in getting rate limited. Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>		2022-10-21 17:14:03 +03:00
..
credentials.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
enterprise.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
init.go	Add profile management in the CLI	2022-06-17 10:58:35 +00:00
log.go	Format message on error	2022-10-21 11:38:16 +03:00
org_instances.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
org_pool.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
organization.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
pool.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
profile.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
provider.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
repo_instances.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
repo_pool.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
repository.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
root.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
runner.go	Start pool managers in the background	2022-10-21 17:14:03 +03:00
version.go	Vendor packages and add Makefile	2022-06-30 10:20:32 +00:00