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

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

Open
wants to merge 1 commit into
base: 7.17
Choose a base branch
from

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.
Cherry-pick of 9de3307 has failed:

On branch mergify/bp/7.17/pr-37158
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 9de3307fab.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG.next.asciidoc

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


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)

# Conflicts:
#	NOTICE.txt
#	go.mod
#	go.sum
@mergify mergify bot requested a review from a team as a code owner November 30, 2023 10:37
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Nov 30, 2023
@mergify mergify bot requested review from faec and leehinman and removed request for a team November 30, 2023 10:37
@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
@elasticmachine
Copy link
Collaborator

💔 Build Failed

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

  • Duration: 7 min 7 sec

Pipeline error 1

This error is likely related to the pipeline itself. Click here
and then you will see the error (either incorrect syntax or an invalid configuration).

❕ Flaky test report

No test was executed to be analysed.

🤖 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!)

@pierrehilbert pierrehilbert requested review from zmoog and removed request for faec and leehinman November 30, 2023 11:11
@zmoog zmoog added the Team:Cloud-Monitoring Label for the Cloud Monitoring team label Nov 30, 2023
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Nov 30, 2023
Copy link
Contributor Author

mergify bot commented Dec 4, 2023

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

14 similar comments
Copy link
Contributor Author

mergify bot commented Dec 11, 2023

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Dec 18, 2023

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Dec 25, 2023

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Jan 1, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Jan 8, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Jan 15, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Jan 22, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Jan 29, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Feb 5, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Feb 12, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Feb 19, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Feb 26, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Mar 4, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Mar 11, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Mar 18, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

7 similar comments
Copy link
Contributor Author

mergify bot commented Mar 25, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Apr 1, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Apr 8, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Apr 15, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Apr 22, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented Apr 29, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented May 6, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented May 13, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.17/pr-37158 upstream/mergify/bp/7.17/pr-37158
git merge upstream/7.17
git push upstream mergify/bp/7.17/pr-37158

Copy link
Contributor Author

mergify bot commented May 13, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

2 similar comments
Copy link
Contributor Author

mergify bot commented May 20, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented May 27, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

Copy link
Contributor Author

mergify bot commented May 27, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/7.17/pr-37158 upstream/mergify/bp/7.17/pr-37158
git merge upstream/7.17
git push upstream mergify/bp/7.17/pr-37158

Copy link
Contributor Author

mergify bot commented Jun 3, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

1 similar comment
Copy link
Contributor Author

mergify bot commented Jun 10, 2024

This pull request has not been merged yet. Could you please review and merge it @zmoog? 🙏

@pierrehilbert
Copy link
Collaborator

@zmoog this one has been opened for a while, what is the plan with this PR?

@zmoog
Copy link
Contributor

zmoog commented Jun 10, 2024

@zmoog this one has been opened for a while, what is the plan with this PR?

Yeah, other priorities are keeping this one behind. It's time to bring it to the finish line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants