fix: ignoring client.knative.dev/nonce changes

[stbarillas]

adding 'client.knative.dev/nonce' to be ignored by lifecycle policy to prevent unnecessary terraform drift.

This addresses this open issue

Fixes: #169

[google-cla[bot]]

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).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[stbarillas]

@prabhu34 @anamer @gtsorbo , I suspect terraform-google-cloud-run-int-trigger is failing because I do not have permissions to that GCP project and lint needs approval. Please advise

[bharathkkb]

/gcbrun

[bharathkkb]

/gcbrun

[stbarillas]

@bharathkkb , I can't view why terraform-google-cloud-run-int-trigger is failing (GCP permissions)

Not sure if this small change would cause the error. Any insight you could share with me?

[apeabody]

@bharathkkb , I can't view why terraform-google-cloud-run-int-trigger is failing (GCP permissions)

Not sure if this small change would cause the error. Any insight you could share with me?

Looks like it might be a flake, re-triggered

[stbarillas]

@bharathkkb , I can't view why terraform-google-cloud-run-int-trigger is failing (GCP permissions) Not sure if this small change would cause the error. Any insight you could share with me?

Looks like it might be a flake, re-triggered

Not sure if still flakey or other issue

[stbarillas]

Could I get another /gcbrun from a collaborator? :) TY!

[prabhu34]

/gcbrun

[stbarillas]

I made the inadvertent mistake of turning off auto-merge. Can a collaborator hit merge for me please :)

Appreciate all the help guys!

[stbarillas]

ping for a merge

[stbarillas]

Ping for a merge

[stbarillas]

Need a /gcbrun from a collaborator and a manual merge afterward

[apeabody]

/gcbrun

[stbarillas]

Thank you apeabody!