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 Azure Event Hubs ingestion fields to google_pubsub_topic #12744

Merged
merged 9 commits into from
Jan 15, 2025

Conversation

andreajialee
Copy link
Contributor

@andreajialee andreajialee commented Jan 13, 2025

Add Azure Event Hubs ingestion fields to google_pubsub_topic

Release Note Template for Downstream PRs (will be copied)

pubsub: added `ingestion_data_source_settings.azure_event_hubs` field to `google_pubsub_topic` resource

@github-actions github-actions bot requested a review from zli82016 January 13, 2025 19:27
Copy link

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@zli82016, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 278 insertions(+))
google-beta provider: Diff ( 3 files changed, 278 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_pubsub_topic (190 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_pubsub_topic" "primary" {
  ingestion_data_source_settings {
    azure_event_hubs {
      client_id           = # value needed
      event_hub           = # value needed
      gcp_service_account = # value needed
      namespace           = # value needed
      resource_group      = # value needed
      subscription_id     = # value needed
      tenant_id           = # value needed
    }
  }
}

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 56
Passed tests: 55
Skipped tests: 1
Affected tests: 0

Click here to see the affected service packages
  • pubsub

🟢 All tests passed!

View the build log

Copy link
Member

@zli82016 zli82016 left a comment

Choose a reason for hiding this comment

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

To fix the fmt and lint errors

@github-actions github-actions bot requested a review from zli82016 January 14, 2025 13:35
@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 278 insertions(+))
google-beta provider: Diff ( 3 files changed, 278 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_pubsub_topic (190 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_pubsub_topic" "primary" {
  ingestion_data_source_settings {
    azure_event_hubs {
      client_id           = # value needed
      event_hub           = # value needed
      gcp_service_account = # value needed
      namespace           = # value needed
      resource_group      = # value needed
      subscription_id     = # value needed
      tenant_id           = # value needed
    }
  }
}

1 similar comment
@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 278 insertions(+))
google-beta provider: Diff ( 3 files changed, 278 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_pubsub_topic (190 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_pubsub_topic" "primary" {
  ingestion_data_source_settings {
    azure_event_hubs {
      client_id           = # value needed
      event_hub           = # value needed
      gcp_service_account = # value needed
      namespace           = # value needed
      resource_group      = # value needed
      subscription_id     = # value needed
      tenant_id           = # value needed
    }
  }
}

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 56
Passed tests: 55
Skipped tests: 1
Affected tests: 0

Click here to see the affected service packages
  • pubsub

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 56
Passed tests: 55
Skipped tests: 1
Affected tests: 0

Click here to see the affected service packages
  • pubsub

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 278 insertions(+))
google-beta provider: Diff ( 3 files changed, 278 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_pubsub_topic (190 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_pubsub_topic" "primary" {
  ingestion_data_source_settings {
    azure_event_hubs {
      client_id           = # value needed
      event_hub           = # value needed
      gcp_service_account = # value needed
      namespace           = # value needed
      resource_group      = # value needed
      subscription_id     = # value needed
      tenant_id           = # value needed
    }
  }
}

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 56
Passed tests: 55
Skipped tests: 1
Affected tests: 0

Click here to see the affected service packages
  • pubsub

🟢 All tests passed!

View the build log

@andreajialee
Copy link
Contributor Author

To fix the fmt and lint errors

Changes are done!

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 310 insertions(+))
google-beta provider: Diff ( 3 files changed, 310 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 57
Passed tests: 55
Skipped tests: 1
Affected tests: 1

Click here to see the affected service packages
  • pubsub

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
  • TestAccPubsubTopic_azureEventHubsIngestionUpdate

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

🟢 Tests passed during RECORDING mode:
TestAccPubsubTopic_azureEventHubsIngestionUpdate [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.


🟢 All tests passed!

View the build log or the debug log for each test

@zli82016
Copy link
Member

@andreajialee , is there a Github issue for this PR? Thanks.

@github-actions github-actions bot requested a review from zli82016 January 15, 2025 09:29
@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 3 files changed, 310 insertions(+))
google-beta provider: Diff ( 3 files changed, 310 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 57
Passed tests: 56
Skipped tests: 1
Affected tests: 0

Click here to see the affected service packages
  • pubsub

🟢 All tests passed!

View the build log

@modular-magician
Copy link
Collaborator

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 4 files changed, 382 insertions(+))
google-beta provider: Diff ( 4 files changed, 382 insertions(+))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))
Open in Cloud Shell: Diff ( 4 files changed, 117 insertions(+))

@modular-magician
Copy link
Collaborator

Tests analytics

Total tests: 58
Passed tests: 55
Skipped tests: 1
Affected tests: 2

Click here to see the affected service packages
  • pubsub

Action taken

Found 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
  • TestAccPubsubTopic_azureEventHubsIngestionUpdate
  • TestAccPubsubTopic_pubsubTopicIngestionAzureEventHubsExample

Get to know how VCR tests work

@modular-magician
Copy link
Collaborator

🟢 Tests passed during RECORDING mode:
TestAccPubsubTopic_azureEventHubsIngestionUpdate [Debug log]
TestAccPubsubTopic_pubsubTopicIngestionAzureEventHubsExample [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.


🟢 All tests passed!

View the build log or the debug log for each test

Copy link
Member

@zli82016 zli82016 left a comment

Choose a reason for hiding this comment

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

LGTM

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

Successfully merging this pull request may close these issues.

3 participants