Skip to content

test: Optional ephemeral values do not have to be set at plan - #39011

Draft
dsa0x wants to merge 3 commits into
mainfrom
sams/only-needed-ephem-variables
Draft

test: Optional ephemeral values do not have to be set at plan#39011
dsa0x wants to merge 3 commits into
mainfrom
sams/only-needed-ephem-variables

Conversation

@dsa0x

@dsa0x dsa0x commented Aug 12, 2026

Copy link
Copy Markdown
Member

ApplyEval expects that the only input variables are ephemeral variables that were non-null at plan time. But the test framework was sending all ephemeral variables, including the ones with a null value. However, such value means that they were also unset during plan, and the null value is a result of the default application to the variable.
Now we

  1. Trigger an error only if the unexpected ephemeral value is non-null.
  2. Ensure that the test framework filters out ephemeral values that the plan deem not required.

Target Release

1.17.x

Rollback Plan

  • If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

@dsa0x dsa0x changed the title test: Set only non-null ephemeral variables for apply time operations test: Optional ephemeral values do not have to be set at plan Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant