Add sensitive flag for two outputs

[hjoh95]

Running a terraform plan using the postgresql module resulted in two errors for these outputs. I believe this is the expected fix

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

For more information, open the CLA check for this pull request.

[comment-bot-dev]

@hjoh95
Thanks for the PR! 🚀
✅ Lint checks have passed.

[morgante]

This is technically not required, because this module is not meant as a root module, but we can add it anyways.

[PhilBrammer]

Isn't this a breaking change, @morgante? I'm assuming that there are implementations that automate/screen against TF APPLY output.

[morgante]

@PhilBrammer I wouldn't consider a sensitive flag a breaking change. It shouldn't impact any automated configuration to switch an output to sensitive, since Terraform can still reference sensitive outputs.

Did this break you in some way?

[PhilBrammer]

Not directly. Working with @hjoh95 on this, but seems to me if I were using this module, I would've been getting a list of instances created as output. Now those would be omitted, correct? And to me, that seems like a breaking change for any consumer expecting this output. Sure they can adapt, but am wondering if this approach is safe "just pushing through" when these modules were being used in the wrong way anyhow? @hjoh95 created a wrapper to use this module correctly.