Added CommandMap check before requesting cluster nodes

[tylerohlsen]

Fixes #2012

[tylerohlsen]

Interesting that this failed with Envoy proxy. It looks like Envoy does actually support RedisCommand.CLUSTER even though their documentation doesn't list it. So should I remove that from the exclusions here?

StackExchange.Redis/src/StackExchange.Redis/CommandMap.cs

Lines 48 to 78 in 6718fea

	/// <summary>
	/// The commands available to <a href="https://github.com/envoyproxy/envoy">envoyproxy</a>.
	/// </summary>
	public static CommandMap Envoyproxy { get; } = CreateImpl(null, exclusions: new HashSet<RedisCommand>
	{
	// see https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/other_protocols/redis.html?highlight=redis
	RedisCommand.KEYS, RedisCommand.MIGRATE, RedisCommand.MOVE, RedisCommand.OBJECT, RedisCommand.RANDOMKEY,
	RedisCommand.RENAME, RedisCommand.RENAMENX, RedisCommand.SORT, RedisCommand.SCAN,
	RedisCommand.BITOP, RedisCommand.MSETNX,
	RedisCommand.BLPOP, RedisCommand.BRPOP, RedisCommand.BRPOPLPUSH, // yeah, me neither!
	RedisCommand.PSUBSCRIBE, RedisCommand.PUBLISH, RedisCommand.PUNSUBSCRIBE, RedisCommand.SUBSCRIBE, RedisCommand.UNSUBSCRIBE,
	RedisCommand.DISCARD, RedisCommand.EXEC, RedisCommand.MULTI, RedisCommand.UNWATCH, RedisCommand.WATCH,
	RedisCommand.SCRIPT,
	RedisCommand.ECHO, RedisCommand.QUIT, RedisCommand.SELECT,
	RedisCommand.BGREWRITEAOF, RedisCommand.BGSAVE, RedisCommand.CLIENT, RedisCommand.CLUSTER, RedisCommand.CONFIG, RedisCommand.DBSIZE,
	RedisCommand.DEBUG, RedisCommand.FLUSHALL, RedisCommand.FLUSHDB, RedisCommand.INFO, RedisCommand.LASTSAVE, RedisCommand.MONITOR, RedisCommand.REPLICAOF,
	RedisCommand.SAVE, RedisCommand.SHUTDOWN, RedisCommand.SLAVEOF, RedisCommand.SLOWLOG, RedisCommand.SYNC, RedisCommand.TIME,
	// supported by envoy but not enabled by stack exchange
	// RedisCommand.BITFIELD,
	//
	// RedisCommand.GEORADIUS_RO,
	// RedisCommand.GEORADIUSBYMEMBER_RO,
	});

[NickCraver]

@tylerohlsen this wasn't you - had a fix pending in #2011. Just merged to bringing main to your branch should help. I think for this PR we should just add a test with it disabled, e.g. a DisabledCommandsStillConnectCluster beside the existing DisabledCommandsStillConnect - thoughts?

[tylerohlsen]

I think for this PR we should just add a test with it disabled, e.g. a DisabledCommandsStillConnectCluster beside the existing DisabledCommandsStillConnect - thoughts?

I certainly can. That might take me a bit longer.

[NickCraver]

@tylerohlsen I gotcha - pushing up a test and release notes!

[NickCraver]

Looking good, thanks @tylerohlsen!

[tylerohlsen]

Awesome! Thanks @NickCraver