TEST UPGRADE TO PROVIDER v3.0.1-rc1 Latest

[patrick-hermann-sva]

https://github.com/Telmate/terraform-provider-proxmox

• UPRGADE PROVIDER

• TEST VM CREATION

• CHECK IF CHANGES NEEDED

  • BECAUSE OF THE UPGRADE
  • OR NEW FEATURES WOULD MAKE THE MODULE BETTER

• THINK ABOUT A POSSIBLE TEST PIPELINE FOR THIS MODULE (WITH REAL APPLY/CREATION)
  "We want to the test this module localy and as a workflow with random data - init/plan/apply/verify or test/destroy"
  "The script should be written in python because we want to use a python action and i know you are familiar with the language"
  "For calling a module we need a (project) folder, a file wich calling the module (localy in this case e.g source = ./), secrets (we have localy or which will be given by the pipeline execution/github) = tfvars file and we need random data e.g. for cpu, ram, datstore (in specific range, tshirt sizes or actual configuration values like name of a network). for storing this data please define a (external) loaded yaml file with the options or ranges which will be loaded in by the script and randomly given for calling/testing the given module."

---
# names should be match what the module expects
vm_count: # list or thing of range notation like 1-3; # should pick one of them randomly
  - 1
  - 2
  - 3
vm_num_cpus: # should pick one of them randomly
  - 2
  - 4
  - 8
  vm_name: #E.G. RANDOM NAME W/ LENGHT XY OR PREFIX MAYBE - UP TO YOU BUT THING OF CONSTRAINS LIKE LENGHT OR FORBIDDEN CHARS LIKE _
pve_datastore: # should pick one of them randomly
  - datastore
  - v3700 

for possible data for our proxmox env - kindly ask @scrum-my gude Mueller

after creating folder, and calling (main).tf file its not needed for the script calling terraform internaly - we will handle in a diffrent step. now we only want to create the possible to call the module for testing