[azure_billing] enable agentless deployment

[jakubgalecki0]

Proposed commit message

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

TL;DR

Buildkite failed before any repo code ran: the agent environment hook could not fetch the GitHub token from Vault (github/token/elastic-integrations-pipeline), so buildkite-agent pipeline upload .buildkite/pipeline.yml exited early. This is a CI configuration/infrastructure issue, not a package code regression in this PR.

Remediation

• Restore/fix Vault token availability for role elastic-integrations-pipeline at path github/token/elastic-integrations-pipeline (or update the hook/role mapping to the correct secret path).
• Re-run the Buildkite build after the secret/path fix.

Investigation details

Root Cause

The failing job (:pipeline::arrow_up: Upload Pipeline: .buildkite/pipeline.yml) fails in the Buildkite agent environment hook before the upload command executes successfully. The hook retries Vault lookup 5 times and consistently gets No value found, then aborts the executor setup.

No failing application/test stack trace was produced, and no repository source file was executed far enough to indicate a PR code defect.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/42408
• Job/step: :pipeline::arrow_up: Upload Pipeline: .buildkite/pipeline.yml
• Key log excerpt:

Attempting to retrieve GitHub token from Vault at path: github/token/elastic-integrations-pipeline
No value found at github/token/elastic-integrations-pipeline
Retry 5/5 exited 2, no more retries left.
Error: Error setting up job executor: running "agent environment" shell hook: The agent environment hook exited with status 1

Verification

• Not run: build fails during agent bootstrap (pre-step), so there is no failing repo command/test to validate locally from this signal.

Follow-up

If this is expected for untrusted fork contexts, gate the upload/bootstrap path to avoid hard-failing when Vault GitHub token access is intentionally unavailable.

Note

🔒 Integrity filter blocked 4 items

The following items were blocked because they don't meet the GitHub integrity level.

• #18848 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [azure_billing] enable agentless deployment #18848 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #18852 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #18848 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 2e14d50

History

• 💔 Build #42408 failed c5132ca
• 💔 Build #42401 failed 8b536f4

[elastic-vault-github-plugin-prod]

Package azure_billing - 1.10.0 containing this change is available at https://epr.elastic.co/package/azure_billing/1.10.0/