Repository navigation
Conversation
meshStack reports for each input of a building block whether a consumer may change it after creation. The Terraform provider needs this to plan a replacement instead of an update that meshStack would reject. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
|
Coverage of the acceptance run against the meshStack backend, on
Uncovered functions
|
|
tfelix
marked this pull request as ready for review
November 19, 2026 10:45
grubmeshi
requested changes
Nov 19, 2026
grubmeshi
approved these changes
Nov 19, 2026
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
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.



meshStack reports for each input of a building block whether a consumer may change it after the building block is created (
updateableByConsumer). The client dropped this field. It now reads it.The Terraform provider needs the field to plan a replacement when such an input changes, see meshcloud/terraform-provider-meshstack#407. Today it plans an in-place update, which meshStack rejects with a 403 for a workspace API key.
The field is a pointer and is never sent: meshStack treats it as read-only.
🤖 Generated with Claude Code