Ben Lambert

@stephenglass thanks for the link there. I'm thinking that we're probably gonna want something like that in place the more the ecosystem grows. Of course we can chose to use...

@stephenglass yeah, a new backend module or something which basically sets these things up could be a good start. It might not do much, but it's possible that in the...

Gonna bring @rugvip here to have a peek as we've spoken about this :pray:

@niallthomson sorry to pull you in here, but do you think that this makes sense? My AWS CodeCommit knowledge is pretty limited and wanted a second pair of eyes. 👍

Hey @jomeier! Thanks for raising this! I think if you're wanting to collect secrets from the frontend, you're going to be best off following this guide: https://backstage.io/docs/features/software-templates/writing-templates/#using-secrets TLDR is you'll...

I wonder if we can make this clearer for users that the `ui:widget: password` is not secure. I'm thinking that there's two options: - We replace the `ui:widget: password` with...

@jomeier no, with `ui:widget` passwords are unfortunately not treated as secure, they are not redacted in logs, and could be accessed / logged through API's. ~~When you use `ui:field: Secret`...

I'm gonna whip up a PR to replace the `ui:widget: password` with our our own `secret` implementation, but I have some concerns that we're going to break existing templates by...

I've put together this: https://github.com/backstage/backstage/pull/24834 happy for some feedback to push it the other way if we think that's a better idea.

> Can I use TemplateSecrets in a seperate custom UI field to access secrets from another ui field? Yes, for sure! > I'm sure it would break templates :D Yeah,...