Skip to content

[azure_metrics] Enable agentless deployment mode#18802

Draft
zmoog wants to merge 2 commits intomainfrom
azure_metrics-enable-agentless
Draft

[azure_metrics] Enable agentless deployment mode#18802
zmoog wants to merge 2 commits intomainfrom
azure_metrics-enable-agentless

Conversation

@zmoog
Copy link
Copy Markdown
Contributor

@zmoog zmoog commented May 5, 2026

Summary

  • Enables agentless deployment mode for all azure_metrics policy templates (Monitor, VM, VM Scaleset, Container Registry/Instance/Service, Database Account, Storage Account).
  • Bumps package version to 1.13.0 and format_version to 3.4.0.

Test plan

  • elastic-package check passes for packages/azure_metrics.
  • Spin up a serverless project and verify the integration is offered in agentless mode.
  • Confirm metrics flow end-to-end for at least one policy template via agentless.

zmoog added 2 commits May 5, 2026 09:29
Enable agentless deployment for all azure_metrics policy templates
(Monitor, VM, VM Scaleset, Container Registry/Instance/Service,
Database Account, Storage Account). Bumps version to 1.13.0 and
format_version to 3.4.0.
@@ -1,3 +1,8 @@
- version: 1.13.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Medium azure_metrics/changelog.yml:1

The new changelog entry declares version: 1.13.0 at line 1, but the next entry in the file is 1.11.0 at line 6, skipping 1.12.0 entirely. This leaves a gap in the version history and breaks the expected sequential ordering of the changelog. The manifest.yml also declares 1.13.0, so the two files are consistent with each other but both skip 1.12.0. Either the version should be 1.12.0 to maintain sequential numbering, or a 1.12.0 entry is missing from the changelog.

- version: 1.13.0
+ version: 1.12.0
🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file packages/azure_metrics/changelog.yml around line 1:

The new changelog entry declares `version: 1.13.0` at line 1, but the next entry in the file is `1.11.0` at line 6, skipping `1.12.0` entirely. This leaves a gap in the version history and breaks the expected sequential ordering of the changelog. The `manifest.yml` also declares `1.13.0`, so the two files are consistent with each other but both skip `1.12.0`. Either the version should be `1.12.0` to maintain sequential numbering, or a `1.12.0` entry is missing from the changelog.

Comment on lines +1 to +5
- version: 1.13.0
changes:
- description: Enable agentless deployment mode for the integration.
type: enhancement
link: https://github.com/elastic/integrations/pull/18802
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟠 High azure_metrics/changelog.yml:1

The changelog entry at line 5 uses the placeholder URL https://github.com/elastic/integrations/pull/999999 instead of the actual PR link. This will be permanently recorded in the release history and breaks the traceability from changelog entry to originating pull request. Replace with the correct PR number before merging.

Suggested change
- version: 1.13.0
changes:
- description: Enable agentless deployment mode for the integration.
type: enhancement
link: https://github.com/elastic/integrations/pull/18802
- version: 1.13.0
changes:
- description: Enable agentless deployment mode for the integration.
type: enhancement
link: https://github.com/elastic/integrations/pull/999999
🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file packages/azure_metrics/changelog.yml around lines 1-5:

The changelog entry at line 5 uses the placeholder URL `https://github.com/elastic/integrations/pull/999999` instead of the actual PR link. This will be permanently recorded in the release history and breaks the traceability from changelog entry to originating pull request. Replace with the correct PR number before merging.

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

@andrewkroh andrewkroh added the Integration:azure_metrics Azure Resource Metrics label May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration:azure_metrics Azure Resource Metrics

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants