sensu / sensu-go

Simple. Scalable. Multi-cloud monitoring.
https://sensu.io
MIT License
1.03k stars 174 forks source link

"sensu-backend init" subcommand missing from CI builds #3439

Closed treydock closed 5 years ago

treydock commented 5 years ago

Expected Behavior

I'd expect #3414 change to be showing up in CI builds, sensu-backend init.

Current Behavior

[root@sensu-backend ~]# sensu-backend init
Error: unknown command "init" for "sensu-backend"
Run 'sensu-backend --help' for usage.
{"component":"sensu-enterprise","error":"unknown command \"init\" for \"sensu-backend\"","level":"fatal","msg":"error executing sensu-backend","time":"2019-11-28T03:38:49Z"}

Context

I wanted to make sure the Puppet module for Sensu was prepared for sensu-backend init change but unable to test.

CC @ghoneycutt

Your Environment

treydock commented 5 years ago

init is missing from help output too:

[root@sensu-backend ~]# sensu-backend -h
sensu backend

Usage:
  sensu-backend [command]

Available Commands:
  help        Help about any command
  start       start the sensu backend
  version     Show the sensu-backend version information

Flags:
  -h, --help   help for sensu-backend

Use "sensu-backend [command] --help" for more information about a command.
echlebek commented 5 years ago

The CI builds are produced from the enterprise product. I've vendored the OSS codebase in there now, so you should be all set.

treydock commented 4 years ago

@echlebek Will this be available now or on next push to master? I am still not seeing init:

[root@sensu-backend ~]# sensu-backend init
Error: unknown command "init" for "sensu-backend"
Run 'sensu-backend --help' for usage.
{"component":"sensu-enterprise","error":"unknown command \"init\" for \"sensu-backend\"","level":"fatal","msg":"error executing sensu-backend","time":"2019-11-30T15:49:59Z"}
[root@sensu-backend ~]# sensu-backend version
sensu-backend version 5.15.0, build 0436b97f7ee6b1a7aa5a23bbdd7b5243239be137, built 2019-11-30T01:36:14Z
echlebek commented 4 years ago

@treydock sorry about that, there was an additional PR that needed to be merged in the enterprise repo. You should be good to go now.