Skip to content

crossplane render generates current lastTransitionTime timestamps that are non-deterministic #50

@bobh66

Description

@bobh66

What happened?

crossplane render is generating status conditions with lastTransitionTime timestamps that have a current time, which means they will never match the content of a previous execution. This makes it impossible to compare the output of two different render command executions.

How can we reproduce it?

Run crossplane render multiple times and observe that the lastTransitionTime timestamps change on each execution.

What environment did it happen in?

  • Crossplane CLI version: 2.3.1
  • Platform (e.g., linux/amd64): linux/amd64

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions