Skip to content

Upgrade Sinks api for eventhub/servicebus IT case - #20343

Merged
saragluna merged 12 commits into
Azure:masterfrom
moarychan:feature/upgrade-reactor-api-for-eventhub-servicebus-it-case
Apr 12, 2021
Merged

Upgrade Sinks api for eventhub/servicebus IT case#20343
saragluna merged 12 commits into
Azure:masterfrom
moarychan:feature/upgrade-reactor-api-for-eventhub-servicebus-it-case

Conversation

@moarychan

@moarychan moarychan commented Apr 2, 2021

Copy link
Copy Markdown
Member

Related PR: Update spring cloud sample for bug modification and api upgrade

Changelog:

  • Upgrade Sinks api for eventhub IT case
  • Move eventhub binder' IT case to test_eventhubs module
  • Enable live test of eventhub binder sample IT case(Test first)

To-do list:

  • The same IT case update for other eventhub samples

@ghost ghost added the azure-spring All azure-spring related issues label Apr 2, 2021
@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@saragluna saragluna self-assigned this Apr 7, 2021
@saragluna saragluna added azure-spring-eventhubs Spring event hubs related issues. azure-spring-servicebus Spring service bus related issues. labels Apr 7, 2021
@check-enforcer

check-enforcer Bot commented Apr 7, 2021

Copy link
Copy Markdown

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

…ture/upgrade-reactor-api-for-eventhub-servicebus-it-case
@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@saragluna

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo

yiliuTo commented Apr 9, 2021

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo

yiliuTo commented Apr 9, 2021

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo

yiliuTo commented Apr 9, 2021

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@yiliuTo

yiliuTo commented Apr 9, 2021

Copy link
Copy Markdown
Member

/azp run java - spring - tests

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@saragluna saragluna left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We should create another PR to address these issue.

cloud:
azure:
eventhub:
connection-string: ${EVENTHUB_CONNECTION_STRING_BINDER}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We could the same event hub namespace and storage account, but a different event hub and storage container.

"value": "[listKeys(resourceId('Microsoft.EventHub/namespaces/authorizationRules', variables('eventHubsNamespaceName'), variables('eventHubsNamespaceKeyName')), '2017-04-01').primaryConnectionString]"
}
}
} No newline at end of file

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

empty line

definition: consume;supply
bindings:
consume-in-0:
destination: binder-test

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

we should think about how to name this destination

"value": "[subscription().subscriptionId]"
}
}
} No newline at end of file

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

empty line

@saragluna saragluna left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM, and another PR to address the above issues.

@saragluna
saragluna merged commit 4ad9a21 into Azure:master Apr 12, 2021
@moarychan
moarychan deleted the feature/upgrade-reactor-api-for-eventhub-servicebus-it-case branch April 15, 2021 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

azure-spring All azure-spring related issues azure-spring-eventhubs Spring event hubs related issues. azure-spring-servicebus Spring service bus related issues.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants