When cloud-function module is used multiple times within project and
default `bundle_config.output_path` is used then all the instances try
to use filename and result is undefined without guarantee to converge to
desired state (i.e. multiple functions may share the same code).
* add `trigger_config_v2` for v2 functions
* add optional for objects in variables.tf
* make examples in README runnable
* add example for Cloud Function v2
* add exapmle for trigger for Cloud Function v2
* remove optional variables from examples with `null` value
* added support 2nd generation cloud function
* changed function_version to a simple boolean v2
removed memory_2ndGen
* will use the var.v2 to add the invoker role
* removed the list uisng compact and formated the code
* formated the code and added conditional feature
* formated the code
* added formating
* resolved the merge conflict
* Update readme
* Create local function object
* added secret_volumes
and secret_environment_variables for CF V2
Co-authored-by: Julio Castillo <jccb@google.com>
* Use uniform access on Cloud Functions buckets.
* Add ALLOW_INTERNAL_AND_GCLB as allowed ingress_settings.
* Enable versiniong if there is lifecycle rule
* Remove only non-current version of objects
* add support for ingress/egress/vpc connector to cloud function
* refactor vpc connector support
* refactor ingress settings support
* fix vpc connector value
* fix vpc connector value
Miren Esnaola
Wiktor Niesiobędzki
Julio Castillo
Maurizio Noseda Pedraglio
maunope
Natalia Strelkova
Somnath Shukla
Ludovico Magnocavallo
Wiktor Niesiobędzki
Simone Ruffilli
apichick
Andras Gyomrey