Added capability meta to generate tf file in workspaces select#287
Merged
Added capability meta to generate tf file in workspaces select#287
Conversation
ssickles
approved these changes
Nov 5, 2025
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
2 participants
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.
This adds
meta(containingsubcategory,platform,subplatform, andoutputNames) to each capability config when generatingcapabilities.tf.tmpl.This alleviates a major problem with capabilities: all capability outputs are combined into a single aggregated result. This means that Terraform must complete all capabilities all at once before the rest of the app module can finish. Instead, this new pattern allows the app module to surgical pull outputs from capabilities that have the desired outputs.
See nullstone-modules/aws-fargate-service#56 for changes that are made as a result of this update.