Could not find consul command. Aborting.

[krishanhettihewa]

Could not find consul command. Aborting.

[brikis98]

Ah, interesting. So do we need a sudo in that command?

[yardbirdsax]

@brikis98 @krishanhettihewa I fixed this in the PR linked above, albeit in a slightly different way, which was to grant read / execute access to everyone on the Consul binary install path. This way the script works as intended (I tested it while calling it with Packer) and also if someone logs in to an instance as a different user they can still execute the Consul binary for troubleshooting / admin purposes.

[yardbirdsax]

Okay we're good now. I ended up going the sudo route after all. I was having to tweak all sorts of permissions to get it working and in the end I didn't want to assume that those permissions should be there on someone's hardened image. This way the script works and it's left up to the user to determine the correct permissions for their needs.

[krishanhettihewa]

Thanks for the response @brikis98. Yes I hope so. it works well, with sudo permissions.

[brikis98]

OK, would you be up for a quick PR to make that change?

[yardbirdsax]

Actually please hold, there might be another issue.