"Wednesday 23rd of August - Engine ID update on an Environment completes but the Environment still is in the same Engine"

[ozcan-ozkaya-et]

Expected Behavior Updated the engine id into a delphix_envrionment within the TF configuration, plans reports as to be updated. Expected to be deleted and created within the new engine.

Actual Behavior delphix_environment is updated successfully but nothing has changed, the resource is still on the previous engine.

Steps To Reproduce the Problem Replace the engine_id on the resource and apply.

Screenshots

Proposed change

Plan result

Apply

Result the Environment is still on the non-prod engine

Version Engines V10 for both DCT v9.0.0 TF provider 2.0.0 TF binary 1.3.9

[nick-mathison]

Hi,

Thanks for the issue report! We are looking to address this issue in a future release.

Please note, that this will likely be a "dumb" deletion and recreation of the environment. If the existing environment has associated dSources and VDBs, we will fail gracefully as it will require copying of data blocks. This could take many hours and have other unintended consequences.

The migration or handling of data blocks is a separate item that would be handled at a DCT level first.

[ozcan-ozkaya-et]

Hi,

Thanks for the issue report! We are looking to address this issue in a future release.

Please note, that this will likely be a "dumb" deletion and recreation of the environment. If the existing environment has associated dSources and VDBs, we will fail gracefully as it will require copying of data blocks. This could take many hours and have other unintended consequences.

The migration or handling of data blocks is a separate item that would be handled at a DCT level first.

Thank you for the response @nick-mathison, I totally understand that when an environment has VDBs and Dsources associated this needs to be handled differently, migrating them first to another environment or deleting them. So in this case a graceful error is expected.