Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update first-party Pulumi dependencies #1735

Merged
merged 1 commit into from
Dec 10, 2024
Merged

Update first-party Pulumi dependencies #1735

merged 1 commit into from
Dec 10, 2024

Conversation

pulumi-renovate[bot]
Copy link
Contributor

@pulumi-renovate pulumi-renovate bot commented Dec 10, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
@pulumi/azuread (source) dependencies patch 6.0.1 -> 6.0.2
@pulumi/gcp (source) dependencies patch 8.10.0 -> 8.10.1
github.com/pulumi/pulumi-azuread/sdk/v5 require major v5.53.5 -> v6.0.2
github.com/pulumi/pulumi-azuread/sdk/v6 require patch v6.0.1 -> v6.0.2
github.com/pulumi/pulumi-gcp/sdk/v8 require patch v8.10.0 -> v8.10.1
github.com/pulumi/pulumi-kubernetes/sdk/v3 require major v3.30.2 -> v4.18.4

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

pulumi/pulumi-azuread (@​pulumi/azuread)

v6.0.2

Compare Source

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

What's Changed

Full Changelog: pulumi/pulumi-azuread@v6.0.1...v6.0.2

pulumi/pulumi-gcp (@​pulumi/gcp)

v8.10.1

Compare Source

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

What's Changed

Full Changelog: pulumi/pulumi-gcp@v8.10.0...v8.10.1

pulumi/pulumi-kubernetes (github.com/pulumi/pulumi-kubernetes/sdk/v3)

v4.18.4

Compare Source

Changed
Fixed

v4.18.3

Compare Source

Fixed

v4.18.2

Compare Source

Fixed

v4.18.1

Compare Source

Added
Changed

v4.18.0

Compare Source

[!IMPORTANT]
The enableSecretMutable and enableConfigMapMutable options may become the default behavior in a future v5 release of the provider.

Programs that depend on the replacement of Secrets and ConfigMaps (e.g. to trigger updates for downstream dependencies like Deployments) are recommended to explicitly specify immutable: true.

Added

  • The new enableSecretMutable provider configuration option treats changes to Secrets as updates instead of replacements (similar to the enableConfigMapMutable option).

    The default replacement behavior can be preserved for a particular Secret by setting its immutable field to true. (https://github.com/pulumi/pulumi-kubernetes/issues/2291)

  • A warning is now emitted if an object has finalizers which might be blocking deletion. (https://github.com/pulumi/pulumi-kubernetes/issues/1418)

  • EXPERIMENTAL: Generic await logic is now available as an opt-in feature. Running a program with PULUMI_K8S_AWAIT_ALL=true will now cause Pulumi to await readiness for all resources, including custom resources.

    Generic readiness is determined according to some well-known conventions (like the "Ready" condition) as determined by cli-utils.

    Pulumi's current behavior, without this feature enabled, is to assume some resources are immediately available, which can cause downstream resources to fail.

    Existing readiness logic is unaffected by this setting. (https://github.com/pulumi/pulumi-kubernetes/issues/2996)

  • EXPERIMENTAL: The pulumi.com/waitFor annotation was introduced to allow for custom readiness checks. This override Pulumi's own await logic for the resource (however the pulumi.com/skipAwait annotation still takes precedence).

    The value of this annotation can take 3 forms:

    1. A string prefixed with jsonpath= followed by a JSONPath expression and an optional value.

      The JSONPath expression accepts the same syntax as kubectl get -o jsonpath={...}.

      If a value is provided, the resource is considered ready when the JSONPath expression evaluates to the same value. For example this resource expects its "phase" field to have a value of "Running":

      `pulumi.com/waitFor: "jsonpath={.status.phase}=Running"`

      If a value is not provided, the resource will be considered ready when any value exists at the given path, similar to kubectl wait --for jsonpath=.... This resource will wait until it has a webhook configured with a CA bundle:

      `pulumi.com/waitFor: "jsonpath={.webhooks[*].clientConfig.caBundle}"`

    2. A string prefixed with condition= followed by the type of the condition and an optional status. This matches the behavior of
      kubectl wait --for=condition=... and will wait until the resource has a matching condition. The expected status defaults to "True" if not specified.

      `pulumi.com/waitFor: "condition=Synced"`

`pulumi.com/waitFor: "condition=Reconciling=False"`

    3. A string containing a JSON array of multiple jsonpath= and condition= expressions.

      `pulumi.com/waitFor: '["jsonpath={.foo}", "condition=Bar"]'`

  • Pulumi will now emit logs for any Kubernetes "Warning" Events associated with resources being created, updated or deleted. (https://github.com/pulumi/pulumi-kubernetes/pull/3135/files)

Fixed

v4.17.1

Compare Source

Fixed

v4.17.0

Compare Source

Changed
Fixed

v4.16.0

Compare Source

Added

  • clusterIdentifier configuration can now be used to manually control the replacement behavior of a provider resource. (https://github.com/pulumi/pulumi-kubernetes/pull/3068)

  • Pod errors now include the pod's last termination state, as well as the pod's termination message if available. (https://github.com/pulumi/pulumi-kubernetes/pull/3091)

    The pod's termination message can be helpful in CrashLoopBackOff situations but will only be reported if it was correctly configured.

    By default, the pod's termination message is read from /dev/termination-log. This location can be configured with terminationMessagePath.

    Use terminationMessagePolicy: FallbackToLogsOnError to use the pod's logs as its termination message.

  • Documentation is now generated for all languages supported by overlay types. (https://github.com/pulumi/pulumi-kubernetes/pull/3107)

Fixed

v4.15.0

Compare Source

Changed
Fixed

v4.14.0

Compare Source

Added
Changed
Fixed

v4.13.1

Compare Source

Added
Changed
Fixed

v4.12.0

Compare Source

Added
Changed
Fixed

v4.11.0

Compare Source

v4.10.0

Compare Source

v4.9.1

Compare Source

v4.9.0

Compare Source

v4.8.1

Compare Source

v4.8.0

Compare Source

v4.7.1

Compare Source

v4.7.0

Compare Source

v4.6.1

Compare Source

v4.6.0

Compare Source

v4.5.6

Compare Source

v4.5.5

Compare Source

v4.5.4

Compare Source

v4.5.3

Compare Source

v4.5.2

Compare Source

v4.4.0

Compare Source

v4.3.0

Compare Source

v4.2.0

Compare Source

v4.1.1

Compare Source

v4.1.0

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "every weekday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@pulumi-renovate pulumi-renovate bot added dependencies Pull requests that update a dependency file impact/no-changelog-required This issue doesn't require a CHANGELOG update labels Dec 10, 2024
@pulumi-renovate pulumi-renovate bot merged commit 5c0a582 into master Dec 10, 2024
42 checks passed
@pulumi-renovate pulumi-renovate bot deleted the renovate/pulumi branch December 10, 2024 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pulumi-renovate-approve pulumi-renovate-approve[bot] pulumi-renovate-approve[bot] approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants