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

[8.11](backport #37158) [Azure] [Billing] Switch to Consumption API 1.1.0 with patches #37242

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 30, 2023

This is an automatic backport of pull request #37158 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Switch to consumption 1.1.0 with patches

The Consumption SDK does not URL encode the query parameters in the
next link when the response requires more than one page to fetch all
the usage details items.

Our Azure SDK for Go fork contains a small patch to URL encode the
next link value and avoid the 400 error.

We also upgraded the azcore package to use the standard URL helper for
the Azure SDK.

* Update NOTICE.txt

* Target tag v1.1.0-elastic instead of the commit

Tidy up the go.mod file by targeting the tag `v1.1.0-elastic` on the
Azure SDK fork instead of the commit.

(cherry picked from commit 9de3307)
@mergify mergify bot requested a review from a team as a code owner November 30, 2023 10:07
@mergify mergify bot added the backport label Nov 30, 2023
@mergify mergify bot assigned zmoog Nov 30, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 30, 2023
@botelastic
Copy link

botelastic bot commented Nov 30, 2023

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-11-30T10:07:38.292+0000

  • Duration: 113 min 23 sec

Test stats 🧪

Test Results
Failed 0
Passed 28457
Skipped 2013
Total 30470

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@zmoog zmoog merged commit 1f282b0 into 8.11 Nov 30, 2023
113 checks passed
@zmoog zmoog deleted the mergify/bp/8.11/pr-37158 branch November 30, 2023 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants