Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add configurable sleep/timeout for GCP VPC peering #247

Merged
merged 5 commits into from
Dec 18, 2023

Conversation

tbroden84
Copy link
Contributor

WHY are these changes introduced?

Reported issues about "Timeout talking to backend" and lack of retries when requesting VPC peering.

Part of: #242
Requires: 84codes/go-api#43

WHAT is this pull request doing?

  • Make retries configurable through sleep and timeout
  • Add sleep/timeout when requesting VPC Peering

HOW can this pull request be tested?

Manual run a workflow with VPC peering to another VPC hosted in GCP.

Comment on lines 283 to 294
## Changelog

List of changes made to this resource for different versions.

[v1.29.0](https://github.com/cloudamqp/terraform-provider-cloudamqp/releases/tag/v1.29.0) configurable
sleep and timeout for retries when requesting and reading peering.

[v1.28.0](https://github.com/cloudamqp/terraform-provider-cloudamqp/releases/tag/v1.18.0)
Added `wait_on_peering_status` as optional, set to wait until peering is finished.

[v1.16.0](https://github.com/cloudamqp/terraform-provider-cloudamqp/releases/tag/v1.16.0)
deprecated intance_id and use vpc_id instead
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see we are discussing this at #246 (comment) :)

Copy link
Member

@dentarg dentarg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, let's see which way we go with the changelogs

@tbroden84 tbroden84 merged commit 51e916c into main Dec 18, 2023
1 check failed
@tbroden84 tbroden84 deleted the gcp-peering-retries branch December 18, 2023 09:17
@dentarg
Copy link
Member

dentarg commented Dec 18, 2023

@tbroden84 I think we should be able to have passing builds before merging here if we always merge / bump go-api first?

@tbroden84
Copy link
Contributor Author

tbroden84 commented Dec 18, 2023

@dentarg yes, my bad this time. Added both PRs in https://github.com/84codes/go-api/releases/tag/v1.15.0, instead of doing two releases. This caused dependency issues for privatelink resource. However ignored it since both PRs was going to be merged after each other.

@dentarg
Copy link
Member

dentarg commented Dec 18, 2023

I see, and we made changes in go-api so it wasn't compatible with main branch either, but that was resolved by f4c76b3

Okay no worries :)

@tbroden84
Copy link
Contributor Author

Yes correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants