Skip to content

test: experiment with making e2e test serve smoke tests#200

Draft
JohannesRudolph wants to merge 4 commits into
mainfrom
feature/smoke-test-foundations
Draft

test: experiment with making e2e test serve smoke tests#200
JohannesRudolph wants to merge 4 commits into
mainfrom
feature/smoke-test-foundations

Conversation

@JohannesRudolph

Copy link
Copy Markdown
Member

e2e test are deploying meshstack_integration.tf and use an ephemeral backplane

smoke tests are running against a long-lived cloud foundation backplane, validating that live, released versions of BBDs in a meshStack are still functional

@github-actions

github-actions Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Scorecard Check

Scorecard run on commit 26843e4012da2270436339cedb17f345eff27d7f relative to origin/main

📊 meshstack-hub Module Scorecard

Generated: 2026-06-10 | Modules scanned: 1 | Categories: 5

📋 Per-Module Category Summary

Score per category per building block. n/a = category does not apply to this module.

Module Overall Core Structure Integration Azure Backplane STACKIT Backplane Testing
stackit/storage-bucket 🟢 96% 🟢 83% 🟢 100% n/a 🟢 100% 🟢 100%

⚠️ 1 module has failing checks — failing categories are expanded below.

Core Structure — some checks failing

Basic module file structure and documentation — applies to 1 modules

Module Score 📦 🔗 📋 📝 🖼️ 📌 🔒
stackit/storage-bucket 🟢 83%

Core Structure — Summary

Emoji Criterion Coverage Status
📦 buildingblock/ directory exists 1/1 🟢 100%
🔗 meshstack_integration.tf present 1/1 🟢 100%
📋 buildingblock/APP_TEAM_README.md present (no-integration fallback) n/a
📝 buildingblock/README.md with YAML front-matter 1/1 🟢 100%
🖼️ buildingblock/logo.png included 1/1 🟢 100%
📌 buildingblock/versions.tf present 1/1 🟢 100%
🔒 Provider versions use minimum constraint (>=) 0/1 🔴 0%
Integration — ✅ all passing

meshstack_integration.tf conventions — applies to 1 modules

Module Score 🏷️ 🏢 📤 🔌 📎 🔀 📋 🏷️ 📖 📝 📊 🚫
stackit/storage-bucket 🟢 100%

Integration — Summary

Emoji Criterion Coverage Status
🏷️ variable "hub" in integration 1/1 🟢 100%
🏢 variable "meshstack" in integration 1/1 🟢 100%
📤 building_block_definition output exposed 1/1 🟢 100%
🔌 meshcloud/meshstack in required_providers 1/1 🟢 100%
📎 backplane source uses var.hub.git_ref 1/1 🟢 100%
🔀 ref_name uses var.hub.git_ref 1/1 🟢 100%
📋 version_spec.draft uses var.hub.bbd_draft 1/1 🟢 100%
🏷️ BBD metadata.tags forwards var.meshstack.tags 1/1 🟢 100%
📖 BBD readme field present 1/1 🟢 100%
📝 BBD readme starts with plain-text description (no heading) 1/1 🟢 100%
📊 BBD readme has shared responsibility table (✅/❌) 1/1 🟢 100%
🚫 No documentation_md output in backplane 1/1 🟢 100%
Azure Backplane — not applicable

Azure UAMI-based automation principal conventions — applies to 0 modules

No applicable modules.

STACKIT Backplane — ✅ all passing

STACKIT WIF-based automation principal conventions — applies to 1 modules

Module Score 🔐 🚫 📤
stackit/storage-bucket 🟢 100%

STACKIT Backplane — Summary

Emoji Criterion Coverage Status
🔐 Uses stackit_service_account_federated_identity_provider 1/1 🟢 100%
🚫 No stackit_service_account_key resource 1/1 🟢 100%
📤 Outputs service_account_email (not key) 1/1 🟢 100%
Buildingblock provider uses use_oidc = true 1/1 🟢 100%
Testing — ✅ all passing

End-to-end test coverage — applies to 1 modules

Module Score ⚙️ 🧪
stackit/storage-bucket 🟢 100%

Testing — Summary

Emoji Criterion Coverage Status
⚙️ backplane/ directory (optional tier) 1/1 🟢 100%
🧪 e2e/ test directory exists 1/1 🟢 100%
e2e/ contains .tftest.hcl files 1/1 🟢 100%

@aws-amplify-eu-central-1

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-200.d1o16zfeoh2slu.amplifyapp.com

e2e test are deploying meshstack_integration.tf and use an ephemeral backplane

smoke tests are running against a long-lived cloud foundation backplane, validating that live, released versions of BBDs in a meshStack are still functional
@JohannesRudolph JohannesRudolph force-pushed the feature/smoke-test-foundations branch from 64a2b9e to b199f3a Compare June 10, 2026 12:33
JohannesRudolph and others added 3 commits June 10, 2026 16:00
…oint

AWS provider v5+ sends LocationConstraint for custom endpoints even when
region = "us-east-1". STACKIT's StorageGRID rejects "us-east-1" as an
invalid location constraint. Using "eu01" matches STACKIT's actual S3
region and is accepted by the CreateBucket API.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…3 eu01 region

STACKIT StorageGRID requires LocationConstraint="eu01" in CreateBucket requests.
AWS provider v5+ sends the configured region as LocationConstraint, so we use
region="eu01". However, the provider validates region names against known AWS
regions — adding skip_region_validation=true allows the non-AWS region name.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…Constraint on CreateBucket

AWS SDK Go v2 (provider >= 5.0) always sends LocationConstraint in CreateBucket requests,
including for us-east-1. STACKIT StorageGRID rejects any LocationConstraint value with
InvalidLocationConstraint. AWS SDK Go v1 (provider ~> 4.0) omits LocationConstraint
entirely when region=us-east-1, which is what StorageGRID requires.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant