Naming Secret (instead of simple_s3_secret, simple_s3_secret_1, ... )

[kentbulza]

Hi @JelteF . Wishing you a wonderful 2026. Could you do something to allow me to set srvname via create_simple_secret() to keep it clearer for people who have numerous secrets? S3 bucket names are often ambiguous: I might have trading partners Walmart, Tesco, and Ahold all with only slightly different (but still globally unique) S3 buckets: s3://trade-partner-bucket , s3://external-trade, s3://partner-incoming. And with a single partner, I might have multiple keys for different paths in the bucket s3://external-trade/ingress, s3://external-trade/egress.

Or do you think this belongs in srvoptions. Or how about both a first-class "label" (srvname) like "walmart_usa_incoming_secret" and "description" (srvoptions.description) for complex explanations ("This is the replacement key pair after re-issue 1/1/2026")?

Or do you feel the utility function should not be used by folks with many secrets?

[JelteF]

Why not use CREATE SERVER directly in that case? create_simple_secret is really just meant as a convenient shortcut. If you want full control, using CREATE SERVER is recommended.

[kentbulza]

Certainly. That was one of the options I mentioned, and I'll take your recommendation.