Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Oct 29, 2025

What does this PR do?

This PR aims to reduce the scope of the legacy kv/ci-shared/observability-ingest/cloud/gcp secret only for the integration-test-matrix pipeline.
This is part of the global process about removing this secret usage.

Why is it important?

It allows us to simplify the pre-command script and to limit the usage of a legacy secret which will be removed in the future.

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

This is an automatic backport of pull request #10734 done by [Mergify](https://mergify.com).

* Reduce the scope of the legacy secrets usage only for integration-test-matrix

* Fix pipeline slug

* Add google oidc plugin in integration tests ech step

* Remove gcp auth plugin usage and fix pre exit command

* Fix typo

* Preserve ESS Credentials logic

* Use parameter expansion instead of adding more logic to reduce the complexity

(cherry picked from commit 41dd43d)
@mergify mergify bot added the backport label Oct 29, 2025
@mergify mergify bot requested review from a team as code owners October 29, 2025 17:35
@mergify mergify bot requested review from pkoutsovasilis and swiatekm and removed request for a team October 29, 2025 17:35
@mergify mergify bot added the backport label Oct 29, 2025
@elasticmachine
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

cc @fr4nc1sc0-r4m0n

Copy link
Contributor

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

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

LGTM
we'll wait to merge it until we have ready the backport from #10906

@v1v
Copy link
Member

v1v commented Oct 30, 2025

we'll wait to merge it until we have ready the backport from #10906

There might be conflicts, if we merge the other one and create the backports - let's merge this one now

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n merged commit 3affcd2 into 9.2 Oct 30, 2025
24 checks passed
@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n deleted the mergify/bp/9.2/pr-10734 branch October 30, 2025 10:58
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.

4 participants