v4.1.4 - corrected errors in port policies.

Full Changelog: v4.1.1...v4.1.4

v4.1.1 - Removing Data Resources

This release changes the data resources back to data objects. In v4.0.1 I attempted to use resources to create pools/policies if a user didn't pre-define the objects. This led to more problems than it solved.

This release moves back to using data objects if a pool/policy has not already been defined.

Full Changelog: v4.0.3...v4.1.1

v4.0.3 - downgrading provider for CVA Support

Full Changelog: v4.0.2...v4.0.3

v4.0.2 - Fixed a few key/value errors.

Full Changelog: v4.0.1...v4.0.2

v4.0.1 - Breaking move to merged Organizations.

In all previous releases of this module organizations have been maintained as separate loops. After having worked with Terraform for the last 3 years I have determined that data objects don't work well with Intersight and Terraform as a data object must exist before referencing the data object. Because the module is written to read pools/policies/profiles at the same time, too often there is the chicken before the egg scenario that rears as a problem.

To move completely away from using data sources for pools and policies there are new resources that will reference objects that are not created by the user data but are referenced in a policy or profile. This isn't optimal because these resources could be duplicate entries, and to prevent them from being accidentally deleted they have been marked as do_not_destroy. So these should only be used when you don't want to maintain the objects with Terraform. Additionally, to reduce the number of these resources that are created this new update to the module merges all organizations into a single loop for each module. This is to limit how often the do_not_destroy resources are created, since policies can now be shared between organizations in Intersight.

The downside to this approach is that any time you are using the do_not_destroy resources is if you want to delete them in the future you must manually remove them from the state file.

Full Changelog: v3.1.5...v4.0.1

v3.1.5 - New BIOS Tokens and Reverting VLANs process

With v3.2.1 - Attempted to reduce plan time by moving VLANs to a data source. This causes the plan to freeze when there are more than 1000 VLANs in a definition. So reverting this back to 3.1.5 and removing VLANs data sources.

Full Changelog: v3.2.1...v3.1.5

v3.2.1 - Changing VLANs to Data Source

Full Changelog: v3.1.4...v3.2.1

v3.1.4 - default policy names for port policies

Full Changelog: v3.1.3...v3.1.4

v3.1.3 - tx queue update for VMware Template

Full Changelog: v3.1.2...v3.1.3

v3.1.2 - filter on length of firmware policy for loop

Full Changelog: v3.1.1...v3.1.2