Skip to content

[aws_billing] Bump version set in the transform destination pipeline#15593

Merged
mrodm merged 3 commits intoelastic:mainfrom
mrodm:fix_transform_aws_billing
Oct 14, 2025
Merged

[aws_billing] Bump version set in the transform destination pipeline#15593
mrodm merged 3 commits intoelastic:mainfrom
mrodm:fix_transform_aws_billing

Conversation

@mrodm
Copy link
Collaborator

@mrodm mrodm commented Oct 7, 2025

Proposed commit message

Fix ingest pipeline name used in the transform destination settings.
Version included in the ingest pipeline name must match the package version set in the manifest.

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

Current Ingest pipelines created when package is installed:
ingest pipelines installed

@mrodm mrodm self-assigned this Oct 7, 2025
@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Oct 7, 2025

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@mrodm mrodm force-pushed the fix_transform_aws_billing branch from ea87ec5 to 0561fb3 Compare October 14, 2025 08:55
@mrodm mrodm marked this pull request as ready for review October 14, 2025 09:57
@mrodm mrodm requested a review from a team as a code owner October 14, 2025 09:57
@mrodm mrodm requested a review from a team October 14, 2025 09:57
dest:
index: "aws_billing.cur-v1"
pipeline: "metrics-aws_billing.cur-0.1.0-pipeline_extract_metadata"
pipeline: "metrics-aws_billing.cur-0.2.0-pipeline_extract_metadata"
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't we actually bump this to 0.2.1? What if someone installs this version 0.2.1 - won't they run into the same problem?

Copy link
Collaborator Author

@mrodm mrodm Oct 14, 2025

Choose a reason for hiding this comment

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

Good catch! I've just used the version in main branch, but I should have set in the transform definition the version of the package set in this PR.

Updated in 078f98d

Thanks!

Copy link
Contributor

@agithomas agithomas left a comment

Choose a reason for hiding this comment

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

LGTM!

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @mrodm

@andrewkroh andrewkroh added the Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] label Oct 14, 2025
@mrodm mrodm requested a review from gpop63 October 14, 2025 13:03
@mrodm mrodm merged commit 678ed33 into elastic:main Oct 14, 2025
7 checks passed
@mrodm mrodm deleted the fix_transform_aws_billing branch October 14, 2025 14:37
@elastic-vault-github-plugin-prod

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

agithomas pushed a commit to agithomas/integrations that referenced this pull request Oct 30, 2025
…lastic#15593)

Fix ingest pipeline name used in the transform destination settings.
Version included in the ingest pipeline name must match the package
version set in the manifest.
tehbooom pushed a commit to tehbooom/integrations that referenced this pull request Nov 19, 2025
…lastic#15593)

Fix ingest pipeline name used in the transform destination settings.
Version included in the ingest pipeline name must match the package
version set in the manifest.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration:aws_billing AWS Cost and Usage Report (CUR 2.0) Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants