Skip to content
This repository was archived by the owner on Jan 20, 2026. It is now read-only.

CAFV-393: Do not update VAppMetadataUpdated anymore - #636

Draft
arunmk wants to merge 1 commit into
vmware-archive:mainfrom
arunmk:ak/CAFV-393
Draft

CAFV-393: Do not update VAppMetadataUpdated anymore#636
arunmk wants to merge 1 commit into
vmware-archive:mainfrom
arunmk:ak/CAFV-393

Conversation

@arunmk

@arunmk arunmk commented Apr 1, 2024

Copy link
Copy Markdown
Contributor

Description

Please provide a brief description of the changes proposed in this Pull Request

  • This stops updating the vAppMetadataUpdated field. The VCDResourceSet already contains the list of vApps consumed by the cluster. This field is not needed anymore.
  • This does not remove any race scenarios.
  • This field can remove the number of VCD API calls while a cluster is being created by 1 call per reentry to the reconciler. That is a small tax when the number of calls is considered. This can be reduced by other means as well.

Checklist

  • tested locally
  • updated any relevant dependencies
  • updated any relevant documentation or examples

API Changes

Are there API changes?

  • Yes
  • No

If yes, please fill in the below

  1. Updated conversions?
    • Yes
    • No
    • N/A
  2. Updated CRDs?
    • Yes
    • No
    • N/A
  3. Updated infrastructure-components.yaml?
    • Yes
    • No
    • N/A
  4. Updated ./examples/capi-quickstart.yaml?
    • Yes
    • No
    • N/A
  5. Updated necessary files under ./infrastructure-vcd/v1.0.0/?
    • Yes
    • No
    • N/A

Issue

If applicable, please reference the relevant issue

Fixes #


This change is Reviewable

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants