Repository navigation
feat: let a foundation e2e test order from a workspace that does not own the definition - #372
Conversation
…own the definition Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Scorecard Check
📊 meshstack-hub Module Scorecard
📋 Per-Module Category SummaryScore per category per building block.
Core Structure — some checks failingBasic module file structure and documentation — applies to 3 modules
Core Structure — Summary
Integration — some checks failingmeshstack_integration.tf conventions — applies to 3 modules
Integration — Summary
AWS Backplane — not applicableAWS automation principal conventions (WIF or cross-account StackSet) — applies to 0 modules No applicable modules. Azure Backplane — not applicableAzure UAMI-based automation principal conventions — applies to 0 modules No applicable modules. GCP Backplane — not applicableGCP workload-identity-federation automation principal conventions — applies to 0 modules No applicable modules. STACKIT Backplane — ✅ all passingSTACKIT WIF-based automation principal conventions — applies to 1 modules
STACKIT Backplane — Summary
Testing — some checks failingEnd-to-end test coverage — applies to 3 modules
Testing — Summary
📈 Overall SummaryOverall Average Score: 97%Score Distribution
|
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
grubmeshi
left a comment
There was a problem hiding this comment.
lgtm, feels like the right approach
A foundation smoke test sometimes has to run in its own workspace, for example when the owner workspace carries tags that a policy uses. Foundation mode now takes an optional
definition_workspacefor the lookup, so the test can order the released version from another workspace.Related: meshcloud/trial-cloudfoundation#22
🤖 Generated with Claude Code