Skip to content

Releases: dominikzorgnotti/VMware-vSphere-Release-Tagging

v1.2.0 Enhancement: Add release tags to the vCenter

17 Mar 21:10
970bf73
Compare
Choose a tag to compare

This release adds the function Set-VcTagByRelease to the PowerShell module which allows to set a tag with the release name to the vCenter itself.

v1.1.2 Bug fixes: Added minimum PowerCLI versions

11 Mar 11:07
Compare
Choose a tag to compare

After feedback that tag assignments fail (Thanks, Christian), the root cause was determined to be an outdated PowerCLI module.
This releases includes a check if the installed PowerCLI version is at least 12.1

v1.1.1 Bug fixes: Added backstops

11 Mar 10:04
Compare
Choose a tag to compare

Added backstops if JSON data is empty or if tags cannot be build

v1.1.0 Optimised core logic in the ESXi tag module

11 Mar 08:25
0b348b8
Compare
Choose a tag to compare

This release addresses #6 and has a much simpler logic to handle the tag creation and assignment to ESXi hosts.
As a side effect, the performance increased and troubleshooting should be easier.

v1.0.1: Major module naming updates

09 Mar 21:57
5f99cd7
Compare
Choose a tag to compare

Starting with v1.0.0 the module has been renamed to VMware vSphere Release Tagging.
This indicates the wider intension tagging not only ESXi but in the future (#4) also vCenter.

A bit of housekeeping, internal variable names have been standardized.

v0.2.1: Fixes in usage examples

09 Mar 17:31
Compare
Choose a tag to compare

Building on the improvements of the v0.2.0 release, v0.2.1 is bug fixing:
Fixed usage examples for the module and added a tighter check for tags in the specific ESXi release category.

v0.2.0: Target scope for tag application

09 Mar 16:24
ed54df3
Compare
Choose a tag to compare

This release adds the optional ability to add a scope (i.e. not all hosts will be tagged) to the module.
This is provided by the the parameter "-Entity" which expects a VI object (e.g. get-cluster "production) as an argument.
Currently, there is no support to pass on the VI object via pipeline ( | )

v0.1.0: Automated data retrieval

08 Mar 09:49
44aa0c0
Compare
Choose a tag to compare

In this release I am addressing the requirement to manually specify a JSON file with the required data as mentioned in #1
Now, the default is trying a direct download from GitHub and the option is to specify a file or custom URL.

Release v0.0.3 - Improved vSphere 6.x data

06 Mar 16:25
1249c16
Compare
Choose a tag to compare

This release switches from the "Release Name" To the "Version" field as a source to build the tags.
The goal is to improve the tags for vSphere versions below 7.