feat(template)!: introducing variables and sensitive configuration

[meganwolf0]

Description

Sample implementation for sensitive and non-sensitive configuration data to support templating

Related Issue

Relates to #641

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Schema Updates applied
• Contributor Guide Steps followed

[brandtkeller]

I am a fan of this direction - called out a few items we may want to think about but otherwise this meets our requirements.

I looked for any concerns or risks present with the nested brace replacement and did not find any issues.

A lot of commonality between our approaches made this an easy review.

[brandtkeller]

Additionally can we update the go mod/sum files when preparing for next review?

[meganwolf0]

Additionally can we update the go mod/sum files when preparing for next review?

When you say update - is there a particular package you were looking at or just like a go mod tidy cleanup?

[meganwolf0]

So I spent a little more time on this then I was initially planning and did some refactor of the internal/template package + the command. I was running into some issues when testing the cmd where the flags getting set were persisting across runs - which is not ideal. I refactored this so that we don't have external to the command flags (which sort of runs counter to what we do in all our other cmds, but I've seen this pattern in other cobra cli usage and tbh I like it better, seems to reduce side effects when testing.)

[brandtkeller]

Super minor inconsistency in the help command. quick modification and re-generation of the cli doc and I'm good!