fix: k8s_callback input structure to match kubernetes-details output schema#332
Open
rauneetverma wants to merge 1 commit intomainfrom
Open
fix: k8s_callback input structure to match kubernetes-details output schema#332rauneetverma wants to merge 1 commit intomainfrom
rauneetverma wants to merge 1 commit intomainfrom
Conversation
…output schema The module's variables.tf expected cluster_endpoint directly on kubernetes_details, but the @facets/kubernetes-details output type nests these under attributes. Updated variables.tf and main.tf to use attributes nesting, and removed the output_name workaround from project-type configs. Co-Authored-By: Claude Opus 4.6 (1M context) <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
k8s_callbackmodule'svariables.tfto nest input fields underattributesto match the@facets/kubernetes-detailsoutput type schemamain.tfreferences fromvar.inputs.kubernetes_details.cluster_endpointtovar.inputs.kubernetes_details.attributes.cluster_endpointoutput_name: attributesworkaround from all three project-type configs (AWS, Azure, GCP)Test plan
cluster_endpointwithout needingoutput_name: attributes🤖 Generated with Claude Code