add helm release addon non-sensitive outputs

[FernandoMiguel]

What does this PR do?

add helm_addons outpus

Motivation

So practitioners can add outputs to modules

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.

For Moderators

• E2E Test successfully complete before merge?

[askulkarni2]

@FernandoMiguel interesting PR. Would you be able to add some more details in the motivation? What is the use-case for being able to consume these outputs? Maybe an code example would help.

Also the CI check is failing. Running pre-commit run terraform_docs should fix that.

[FernandoMiguel]

@askulkarni2 I was looking to get the version of the charts installed, and also looking for newer versions that I could upgrade to.
For now, I submitted this just for the helm addon module, and if it accepted I'll open a PR adding outputs to the addons themselves.

I also have a single liner that does what this does, but without descriptions, and also includes the sets and value files, if the team prefers that.
output "helm_release_external_dns" { value = try({ for k, v in helm_release.external-dns : k => (k != "repository_password" ? v : null) }, null) }

if you can provide me with further instructions on the pre-commit command, I can try that tomorrow.

[bryantbiggs]

instead of adding all outputs, would it be possible to only export the outputs that are needed? we could also do a single full export like:

output "helm_release" {
  description = "Attributes of Helm release created"
  value       = helm_release.addon
}

[FernandoMiguel]

instead of adding all outputs, would it be possible to only export the outputs that are needed? we could also do a single full export like:

output "helm_release" {
  description = "Attributes of Helm release created"
  value       = helm_release.addon
}

The password attribute is sensitive and would block the all output downstream.

[FernandoMiguel]

Pls review.
Thank you.

[bryantbiggs]

I think the value here would be:

value = try({ for k, v in helm_release.addon : k => v if k != "repository_password" }, {})

[FernandoMiguel]

Either works in my testing.
I tend to go with not setting explicitly anything, hence null.
But not all providers handle that well.
I'm fine following your existing style, if you prefer.

[bryantbiggs]

see comment above and it looks like there are CI failures to address (pre-commit)

Updated output

[FernandoMiguel]

thank you for picking up this @bryantbiggs
I was away from the computer part of last week.