Repository navigation
Release/26.10 - #104
Open
Andy Hay (Andy-Hay) wants to merge 10 commits into
Open
Release/26.10#104Andy Hay (Andy-Hay) wants to merge 10 commits into
Andy Hay (Andy-Hay) wants to merge 10 commits into
Conversation
Updates every snowplow-devops module used across the AWS, GCP and Azure examples to the releases that move module CI to Node 24 with SHA-pinned actions and bump the telemetry module to 0.6.3. Also moves google lb from 0.3.0 to 0.4.2, picking up the optional HTTP to HTTPS redirect (off by default) and the unique URL map name fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Point the Installation Guide at the current self-hosted quick start page, remove the Documentation table images whose CDN URLs now return 404, and link the release badge to this repo's releases instead of snowplow/snowplow, which stops at 22.01. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Fix Azure deployment summary labels, which said Snowflake, and note that both Azure pipelines load via the Lake Loader - Add the AWS S3 loader target to the platforms table - Move docs links to the current self-hosted and licensing paths so the warehouse and cloud selectors are no longer lost in a redirect - Describe the repo as a self-hosted pipeline rather than Community - Add the Azure directories to the terraform-docs example - Remove the unused deploy-image reference - Update copyright to 2021-current Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The CloudFront images are being restored, so bring back the image row in the Documentation table and its link references. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub is deprecating the Node 20 runtime for Actions. Move every action in ci.yml to its latest release and pin each one to a full commit SHA, with the release version kept in a trailing comment. - actions/checkout v3 -> v7.0.1 (node24) - tj-actions/branch-names v8 -> v9.0.2 (composite, includes the unsafe outputs security fix) - dflook/terraform-validate v1 -> v3.1.0 (docker) - dflook/terraform-fmt-check v1 -> v3.1.0 (docker) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Picks up the patch releases of the eight AWS application modules that move them to service-ec2 0.3.5, which in turn uses tags 0.2.2: - collector-kinesis-ec2 0.10.3 - databricks-loader-ec2 0.3.2 - enrich-kinesis-ec2 0.7.3 - iglu-server-ec2 0.6.3 - redshift-loader-ec2 0.4.2 - s3-loader-kinesis-ec2 0.6.2 - snowflake-streaming-loader-ec2 0.2.3 - transformer-kinesis-ec2 0.5.2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Set fail-fast to false so one failing module directory no longer cancels the validate and fmt checks for the others. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lake-loader-vmss 0.4.1 requires azuread ~> 2.53.1, which doesn't overlap the previous >= 2.43.0, < 2.44.0 pin, so terraform init would fail once the module is released. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepares the 26.10 release. It updates every
snowplow-devopsmodule to the patch releases that move module CI to Node 24 and bump telemetry to 0.6.3, moves this repo's own CI past the Node 20 deprecation, and fixes outdated content in the README.Note
All module releases this PR depends on are published, and
terraform validateandfmtpass in all 11 directories in CI.Module version bumps
Updates 30 modules in the AWS, GCP and Azure examples: 72
versionpins in the.tffiles, and the matching rows in each example's terraform-docs README.Every bump is a patch release. The eight AWS application modules move two patch versions: the first release updates their CI, telemetry and⚠️ ), which goes from
ec2-instance-type-metrics, and the second moves them toservice-ec20.3.5, which usestags0.2.2. The exception isterraform-google-lb(0.3.0to0.4.2because the repo never picked up 0.4.x. The changes in between add an optionalredirect_http_to_httpsinput (defaultfalse) and make the URL map name unique. It should be backwards compatible.Module versions and release PRs
terraform-aws-albterraform-aws-collector-kinesis-ec2terraform-aws-databricks-loader-ec2terraform-aws-enrich-kinesis-ec2terraform-aws-iglu-server-ec2terraform-aws-kinesis-streamterraform-aws-rdsterraform-aws-redshift-loader-ec2terraform-aws-s3-bucketterraform-aws-s3-loader-kinesis-ec2terraform-aws-snowflake-streaming-loader-ec2terraform-aws-transformer-kinesis-ec2terraform-azurerm-collector-event-hub-vmssterraform-azurerm-enrich-event-hub-vmssterraform-azurerm-event-hubterraform-azurerm-event-hub-namespaceterraform-azurerm-iglu-server-vmssterraform-azurerm-lake-loader-vmssterraform-azurerm-lbterraform-azurerm-postgresql-serverterraform-azurerm-storage-accountterraform-azurerm-storage-containerterraform-azurerm-vnetterraform-google-bigquery-loader-pubsub-ceterraform-google-cloud-sqlterraform-google-collector-pubsub-ceterraform-google-enrich-pubsub-ceterraform-google-iglu-server-ceterraform-google-lbterraform-google-pubsub-topicAzure provider constraint
terraform/azure/pipelinenow requiresazuread ~> 2.53.1instead of>= 2.43.0, < 2.44.0.lake-loader-vmss0.4.1 pinsazuread ~> 2.53.1, and the two ranges don't overlap, soterraform initwould fail once the module is released. The directory doesn't useazureaditself, so the old pin only existed for the lake loader. I validated all three Azure directories against the unreleased Azure module code: they resolveazurerm4.27.0 andazuread2.53.1.CI: Node 24 and SHA-pinned actions
Moves each action in
ci.ymlto its latest release and pins it to a full commit SHA, with the version kept in a trailing comment. This clears theNode.js 20 is deprecated … actions/checkout@v3warning.actions/checkoutv33d3c42e5…(v7.0.1)tj-actions/branch-namesv852504926…(v9.0.2)dflook/terraform-validatev129a791ea…(v3.1.0)dflook/terraform-fmt-checkv1e3f43c85…(v3.1.0)The major-version jumps don't change anything this workflow uses: the
dflookactions still takepath, andbranch-namesstill outputscurrent_branch.branch-namesv9 also includes a security fix for unsafe outputs.README
26.10, and it links to this repo's releases instead ofsnowplow/snowplow, whose releases stop at 22.01.get-started/self-hosted/andlicensing/paths. This fixes the Installation Guide link, which returned 404, and keeps the?warehouse=…&cloud=…part of the Deployment Summary links, which the old redirects dropped.deploy-imagereference, and changed the copyright to2021-current.techdocs.png,roadmap.png) currently return 404. They'll show again once the CloudFront files are restored.Testing
terraform fmt -check -recursivepassesfail-fast: false, so each directory reports separately)terraform validatepasses in all four AWS directories (checked locally against the published modules)terraform validatepasses in all four GCP directoriesterraform validatepasses in all three Azure directories🤖 Generated with Claude Code