Feature request: can we add "description" metadata fields to secrets? That way we'd be able to do things like: • add a github link to source code that calls it • add a link to documentation for the envvar • add TODOs about "we really shouldn't do this, but this works so we are" • add links to tickets • add notes about what system/product/feature we use that requires it I would consider this information low-sensitivity and don't care for any special KMS-style heightened encryption - in my threat model it's pretty much the same sensitivity as the secret/env var name. Even just like 1KiB of text would be useful, although ideally it'd be more like 10KiB or even 100KiB so I don't have to think about it. This has long been one of my biggest pain points with practically every secret manager out there, and I regularly do stuff like

GITHUB_TOKEN_SAM

if I'm storing a PAT for something that needs a PAT and there's no straightforward machine identity mechanism, so that way if the token expires or someone needs to figure out who to ask they know to ask me - but I can only embed so much metadata in the secret name.

HI Sam! Have you considered using Infisical comments?

Hmm - oh, this is interesting. It kinda does, but the UX feels really unsatisfactory: • P1 for my ask: Is it correct that you can only comment on specific secret values? That is, I see that I can comment on

NOTION_BOUNDARY_BOT_TOKEN

in

Development

but I can't comment on

NOTION_BOUNDARY_BOT_TOKEN

, at least not in a way that I can see from

/secret-management/{projectId}/overview

• P2: I want a readonly view of the comment, I don't want to have to ignore my blinking cursor. In fact it's rather jarring that I don't have an explicit call-to-action to begin editing (see previous thread) I was imagining a "description" field between "key" and "environment" in the overview table

This is very useful feedback! Let me note those down for our team and we will follow up with any updates 🙂

Thanks! Can you confirm whether or not my understanding of the current state of it is correct?

Indeed, currently you have to assign comments within the environment and comments are not shared across. Actually, could you please elaborate a bit on what you mean by P2?

> • P2: I want a readonly view of the comment, I don't want to have to ignore my blinking cursor. In fact it's rather jarring that I don't have an explicit call-to-action to begin editing (see previous thread) in notion once a comment is posted, it is readonly by default to interact with it. i have to click "edit" to be able to edit the comment. in infisical, if i add a comment, clicking on the comment immediately puts me in an editing flow and that's really jarring to me editing secret names and values has the same issue for me: by default i do not want to edit secrets, i only want to copy them. primarily i am in one of two states when i'm adding secrets: either i'm rotating an existing one or i'm setting up new infrastructure (as a seed-stage startup, this happens every other month or so) and i'm bulk adding secrets. the default otherwise is "i am trying to debug a thing that is going on or i'm trying to run a new process with existing secrets" in which case i do not want to be editing my secrets

Hi @Sam Lijin! Thank you for providing more details. I submitted this feedback to our team and we will take a look when we do the next iteration of the dashboard 🙏