Skip to content

fix(ci): Use correct READ_ONLY access value instead of READ#7239

Merged
nuugen merged 1 commit intomainfrom
nuugen-patch
Mar 6, 2025
Merged

fix(ci): Use correct READ_ONLY access value instead of READ#7239
nuugen merged 1 commit intomainfrom
nuugen-patch

Conversation

@nuugen
Copy link
Copy Markdown
Member

@nuugen nuugen commented Mar 6, 2025

What does this PR do?

Fix the incorrect pipeline access value from READ to READ_ONLY. This was prompted by the validation failure at https://buildkite.com/elastic/terrazzo/builds/23681#01956b3e-2e25-45b3-bd6c-537cc5b00496.

Why is it important?

Such that the pipeline is managed correctly by EngProd's automation.

Also, this can be prevented once #7240 is merged.

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?
  • ...

@nuugen nuugen requested a review from a team as a code owner March 6, 2025 12:07
@mergify mergify bot assigned nuugen Mar 6, 2025
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Mar 6, 2025

This pull request does not have a backport label. Could you fix it @nuugen? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

Copy link
Copy Markdown
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

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

LGTM

@nuugen nuugen enabled auto-merge (squash) March 6, 2025 12:48
@nuugen nuugen disabled auto-merge March 6, 2025 12:49
@nuugen nuugen enabled auto-merge (squash) March 6, 2025 12:59
@elastic-sonarqube
Copy link
Copy Markdown

@nuugen nuugen merged commit f69f509 into main Mar 6, 2025
12 of 13 checks passed
@nuugen nuugen deleted the nuugen-patch branch March 6, 2025 13:51
@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

cc @nuugen

access_level: BUILD_AND_READ
everyone:
access_level: READ
access_level: READ_ONLY
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.

I think I took the above access level called BUILD_AND_READ and removed BUILD_AND, assuming it was enough :/ . It's undoubtedly misleading that _ONLY is needed; what else will be read if it's only read? Thanks for the fix Linh!

v1v added a commit to pkoutsovasilis/elastic-agent that referenced this pull request Mar 6, 2025
* upstream/main:
  feat: bump go to 1.24.0 (elastic#6932)
  [CI] Fix Core DRA crossbuild (elastic#7203)
  fix(ci): Use correct `READ_ONLY` access value instead of `READ` (elastic#7239)
  ci(buildkite): add initial elastic-agent-helm-charts pipeline (elastic#7176)
  chore: update elastic-agent-libs to v0.18.8 (elastic#6938)
  [flakiness] Correct group for TestEndpointAgentServiceMonitoring (elastic#7165)
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