Get the Project¶

You can choose between two options to get the source code:

Download the latest release from GitHub.
Clone the repository from GitHub.

Download the Latest Release Clone the Repository

TAG_NAME=$(curl -s https://api.github.com/repos/vmware-samples/packer-examples-for-vsphere/releases | jq  -r '.[0].tag_name')
TARBALL_URL=$(curl -s https://api.github.com/repos/vmware-samples/packer-examples-for-vsphere/releases | jq  -r '.[0].tarball_url')

mkdir packer-examples-for-vsphere
cd packer-examples-for-vsphere
curl -sL $TARBALL_URL | tar xvfz - --strip-components 1
git init -b main
git add .
git commit -m "chore: initial commit"
git switch -c $TAG_NAME HEAD

TAG_NAME=$(curl -s https://api.github.com/repos/vmware-samples/packer-examples-for-vsphere/releases | jq  -r '.[0].tag_name')

git clone https://github.com/vmware-samples/packer-examples-for-vsphere.git
cd packer-examples-for-vsphere
git switch -c $TAG_NAME $TAG_NAME

Prerelease Updates

You may also clone the develop branch for the latest prerelease updates.

There could be bugs or breaking changes in flight.

Branches

A branch is mandatory since it is used for the build version and in the virtual machine name. It can be based on the HEAD or a release tag.

Project Structure¶

The directory structure of the project.

Directory	Description
`ansible`	Contains the Ansible roles to prepare Linux machine image builds.
`artifacts`	Contains the OVF artifacts exported by the builds, if enabled.
`builds`	Contains the templates, variables, and configuration files for the machine image builds.
`manifests`	Manifests created after the completion of the machine image builds.
`scripts`	Contains the scripts to initialize and prepare Windows machine image builds.
`terraform`	Contains example Terraform plans to create a custom role and test machine image builds.

Forking the Project

When forking the project for upstream contribution, please be mindful not to make changes that may expose your sensitive information, such as passwords, keys, certificates, etc.