Fix Workload Identity templating not correctly handling uint values#61735
Merged
strideynet merged 1 commit intomasterfrom Nov 24, 2025
Merged
Fix Workload Identity templating not correctly handling uint values#61735strideynet merged 1 commit intomasterfrom
strideynet merged 1 commit intomasterfrom
Conversation
rosstimothy
approved these changes
Nov 24, 2025
Contributor
|
@strideynet See the table below for backport results.
|
This was referenced Nov 24, 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
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.
Noticed this whilst preparing a demo, trying to template in the value of
workload.unix.uidwould lead to a "expression did not evaluate to a string" error. It looks like this issue was specifically related to handling uint attributes. I've also extended the test suite to cover this error.changelog: Fixed workload identity templating to support certain numeric values that previously gave a "expression did not evaluate to a string" error.