chore: skips teardown for secure-cloud-func-internal-server

[g-awmalik]

No description provided.

[prabhu34]

LGTM if the build succeeds!

[apeabody]

Probably should open an issue and label this PR as chore: or chore(CI): as this only changes the CI, not the module.

[daniel-cit]

@apeabody Could you please update this PR?

[daniel-cit]

@g-awmalik looking at the changes, this Pull Request is skipping the whole secure-cloud-func-internal-server tests , not only the teardown (destroy) phase .

Is this the original intent ?

[daniel-cit]

@g-awmalik to skip the teardown phaser of the secure examples wouldn't be enough to comment out this ones:

• https://github.com/GoogleCloudPlatform/terraform-google-cloud-functions/blob/main/build/int.cloudbuild.yaml#L72C1-L79C33

• https://github.com/GoogleCloudPlatform/terraform-google-cloud-functions/blob/main/build/int.cloudbuild.yaml#L97C1-L104C45

• https://github.com/GoogleCloudPlatform/terraform-google-cloud-functions/blob/main/build/int.cloudbuild.yaml#L141C1-L148C38

[prabhu34]

@g-awmalik looking at the changes, this Pull Request is skipping the whole secure-cloud-func-internal-server tests , not only the teardown (destroy) phase .

Is this the original intent ?

No, definitely not the intent. The teardown was commented out and left stale resources in the project. Was unable to proceed further and I had to comment the entire secure-cloud-func-internal-server to debug the issue.

[apeabody]

@g-awmalik - The added retry during the teardown appears to have worked around the issue: #112

[github-actions]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days