chore: Add alternate defaults for mysql & postgresql blueprint

[qz267]

More details in http://docs/document/d/1LMsDRy0zMKQrPUDJ4chlPtqul9bwXs90QH6N8xqZ78I?tab=t.0#heading=h.qx5xjbm73vyx

[imrannayer]

@qz267 is there any reason for changing defaults instead of sending values and override it in module call?

[qz267]

@qz267 is there any reason for changing defaults instead of sending values and override it in module call?

Sorry for the confusion, I was trying to surface some of my WIP changes, to ask for early feedbacks, PR title updated.

b/362377949 is the original request, I don't have strong preference about update in variables or override them in the module call, any suggestions are welcomed, thanks!

[imrannayer]

@qz267 I think it will be better to take alternate route instead of changing defaults in the module as this change will require all the existing user of the module to adjust code for new defaults.

@bharathkkb can u plz review?

[qz267]

I got @q2w suggested using alt_defaults instead https://github.com/GoogleCloudPlatform/cloud-foundation-toolkit/blob/master/cli/bpmetadata/proto/bpmetadata_ui.proto#L149, WDYT?

[q2w]

@qz267 We should also update for modules/postgresql.

[q2w]

/gcbrun