sync-versions

You can sync container image versions by scanning the Terraform blueprint_files.tf file for image fields and updating SOFTWARE_VERSIONS.md to match the extracted tags. The process groups images by starter pack and size while preserving the existing table formatting.

The best way to track version changes is by comparing extracted container image references from Terraform against the existing SOFTWARE_VERSIONS.md documentation. This flags version changes, new images, and removals before deployment to ensure docs are current.

Yes, you can automatically update a versions doc by parsing the blueprint_files.tf Terraform file for container_image and image fields. The extracted tags are applied directly to SOFTWARE_VERSIONS.md while maintaining the repository's starter pack and size structure.

Yes, the version synchronization process preserves the existing table structure in SOFTWARE_VERSIONS.md. It applies changes by grouping extracted container images into the predefined starter pack and size categories without breaking the original documentation formatting.

You should synchronize your container version docs with Terraform files right before deploying to ensure the SOFTWARE_VERSIONS.md file accurately reflects the container image tags defined in blueprint_files.tf. This prevents documentation drift during releases.

Your SOFTWARE_VERSIONS.md file shows outdated container image tags because it was not updated after changes were made to the blueprint_files.tf Terraform configuration. Synchronizing the files resolves this by extracting current image tags and updating the documentation.