Skip to content

Conversation

@pkalsi97
Copy link
Contributor

Closes #6341

Changes:

  • Add DeploymentTimestamp field to IntegrationStatus
  • Set DeploymentTimestamp when transitioning to Deploying phase
  • Update integrationUpdateFunc to prioritize DeploymentTimestamp
  • Add unit tests for timestamp selection logic
  • Extend E2E test to verify DeploymentTimestamp behavior

@pkalsi97 pkalsi97 changed the title fix: Correct first-readiness metric for dry-build integrations fix(ctrl): dry build - correct first-readiness metric Dec 13, 2025
Copy link
Contributor

@squakez squakez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job! Thanks for the contribution!

@github-actions
Copy link
Contributor

⚠️ Unit test coverage report - coverage decreased from 51.6% to 51.5% (-0.1%)

@pkalsi97
Copy link
Contributor Author

@squakez I think the test failure is happening because I did not commit the updated CRDs ? am I thinking correctly here ?
I am also working on the caCert trait option for trusted root certificates issue. do we have to commit the CRDs that we locally generate ?

@squakez
Copy link
Contributor

squakez commented Dec 14, 2025

@squakez I think the test failure is happening because I did not commit the updated CRDs ? am I thinking correctly here ? I am also working on the caCert trait option for trusted root certificates issue. do we have to commit the CRDs that we locally generate ?

Yes. If any change in the crds, make generate is required.

@squakez squakez merged commit dfd4353 into apache:main Dec 15, 2025
10 checks passed
@pkalsi97 pkalsi97 deleted the fix/6341 branch December 15, 2025 08:06
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.

Dry build - first readiness info

3 participants