Consul CLI not parsing "-base64" command line argument correctly

[ktzvetanov]

If you have a question, please direct it to the
consul mailing list if it hasn't been
addressed in either the FAQ or in one
of the Consul Guides.

When filing a bug, please include the following:

consul version for both Client and Server

Client: Consul v0.8.4+ent
Server: Consul v0.8.4+ent

consul info for both Client and Server

Client:
Consul v0.8.4+ent
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
agent:
check_monitors = 0
check_ttls = 4
checks = 4
services = 10
build:
prerelease =
revision = c7098dd+
version = 0.8.4+ent
consul:
bootstrap = false
known_datacenters = 1
leader = false
leader_addr = X.X.X.54:8300
server = true
raft:
applied_index = 2682405
commit_index = 2682405
fsm_pending = 0
last_contact = 54.430728ms
last_log_index = 2682405
last_log_term = 69
last_snapshot_index = 2674298
last_snapshot_term = 69
latest_configuration = [{Suffrage:Voter ID:X.X.X.69:8300 Address:X.X.X.69:8300} {Suffrage:Voter ID:X.X.X.245:8300 Address:X.X.X.245:8300} {Suffrage:Voter ID:X.X.X.54:8300 Address:X.X.X.54:8300} {Suffrage:Voter ID:Y.Y.Y.252:8300 Address:Y.Y.Y.252:8300}]
latest_configuration_index = 1609332
num_peers = 3
protocol_version = 2
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Follower
term = 69
runtime:
arch = amd64
cpu_count = 8
goroutines = 89
max_procs = 8
os = linux
version = go1.8.3
serf_lan:
coordinate_resets = 0
encrypted = false
event_queue = 0
event_time = 17
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 10
members = 4
query_queue = 0
query_time = 2
serf_wan:
coordinate_resets = 0
encrypted = false
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 17
members = 4
query_queue = 0
query_time = 2

Server:
same as above

Operating system and Environment details

Description of the Issue (and unexpected/desired result)

Reproduction steps

XXX:/keys2$ consul kv get -base64 vault/logical/3a2e56f6-e6b5-f929-ce07-07de0cf18fd6/test1
?HFu?|`\qhI?
??hq?4R?Vҍ?????G?DY??]ـ
XXX:/keys2$

VS

XXX:~/keys2$ consul kv get -recurse -base64 vault/logical/3a2e56f6-XXX-07de0cf18fd6/test1
vault/logical/3a2e56f6-XXX-07de0cf18fd6/test1:AAAAAQLhk0hGdYB8YFxxaEnfEQx+r7kRaHHjNFLFVtKNksrX6bMAF36TR85EWZLhXdmA

If I only supply "-base64" I get the binary representation. If I supply "-recurse" the base64 parameter is honored.

Log Fragments or Link to gist

Include appropriate Client or Server log fragments. If the log is longer
than a few dozen lines, please include the URL to the
gist.

TIP: Use -log-level=TRACE on the client and server to capture the maximum log detail.