Skip to content

Conversation

@blampe
Copy link
Contributor

@blampe blampe commented Nov 6, 2025

4.24.0 (November 5, 2025)

Added

Changed

  • The pulumi.com/waitFor annotation now uses an
    RFC9535-compliant JSONPath
    parser. This makes it possible to wait for more complex scenarios.

    For example:

    • To wait for a Pod's status.phase to be "Running" or "Succeeded":

      pulumi.com/waitFor: "jsonpath={.status[?@ == 'Running' || @ == 'Succeeded' ]}"

    • To wait for for an object to have a "Failed" or "Complete" condition with
      a "True" value:

      pulumi.com/waitFor: "jsonpath={.conditions[?(@.type=='Failed'||@.type=='Complete')].status}=True

    (Tools like jsonpath.com are very helpful for
    ensuring your JSONPath expression works as expected.)

    Importantly, please note that kubectl wait --for=jsonpath=... supports only
    a subset of RFC9535. This means some complex waitFor annotations will not
    be reproducible with kubectl.

    Existing expressions should continue to work normally with one notable
    exception: a selector like .items[] now requires an explicit wildcard, i.e.
    .items[*].

    As a reminder, the pulumi.com/waitFor annotation is experimental and
    subject to change. Similarly, RFC9535 is still only proposed and may also
    change in the future.

  • enableConfigMapMutable and enableSecretMutable are now stable.
    (Remove the 'BETA FEATURE' status in front of enableConfigMapMutable and enableSecretMutable provider properties #3886)

Fixed

@blampe blampe enabled auto-merge (squash) November 6, 2025 19:15
@blampe blampe added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

impact/no-changelog-required This issue doesn't require a CHANGELOG update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant