Due to V1 API behavior we have been running into issues with terraform drifting due to values changes from initial server creation to server created process.
While trying to solve these pain points we have a found a few other API V1 constraints which have been addressed.
Users now do not have to know the corresponding os_id for
app
iso
snapshot
If you define snapshot_id, iso_id or app_id we now handle adding the proper os_id.
NOTE If you set os_id with either app_id, iso_id, or snapshot_id an error will be thrown
If you want to use a startup script you can either use a regular boot script with an app_id or regular os_id
However if you want to use a pxe script then you will need to use the os_id = 159
Also note this shouldn't break backwards comp since the desired TF state should still match the defined TF state since the os_id will match up with what TF gets back from the API
Related Issues
96
Checklist:
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you linted your code locally prior to submission?
[x] Have you successfully ran tests with your changes locally?
Description
Due to V1 API behavior we have been running into issues with terraform drifting due to values changes from initial server creation to server created process.
While trying to solve these pain points we have a found a few other API V1 constraints which have been addressed.
Users now do not have to know the corresponding
os_idforIf you define
snapshot_id,iso_idorapp_idwe now handle adding the properos_id.If you want to deploy a regular os you can define your
os_id. https://api.vultr.com/v1/os/listNOTE If you set os_id with either
app_id,iso_id, orsnapshot_idan error will be thrownIf you want to use a startup script you can either use a regular
bootscript with anapp_idor regularos_idHowever if you want to use a
pxescript then you will need to use theos_id = 159Also note this shouldn't break backwards comp since the desired TF state should still match the defined TF state since the
os_idwill match up with what TF gets back from the APIRelated Issues
96
Checklist: