terraform-provider-dynatrace
terraform-provider-dynatrace copied to clipboard
Way to accepts remote changes into state
Is your feature request related to a problem? Please describe. The problem is that dynatrace has UI)), and 90% of things are better to CREATE and VALIDATE for UI That means incoming remote changes are just a fact. The creation of any complex entity for code - it is in 90% is a waste of time. Since we need validation at first and UI has great help.
Examples: SLO - try to validate bгrn rate in code Naming rules - try to validate matching in code Auto tags - try to validate in code etc. everything that needs adjustment and validation is better to do in UI
Config from code in Dynatrace on CREATION stage it is "fire and forget".
Describe the solution you'd like During a conversation with the Terraform forum, I realised that there is no unique API to fulfil these needs. Just because Terraform's ideology is different.
Use case: WHEN I make changes in the UI AND pull changes by Terraform THEN remote configuration should replace the old configuration in the state
Describe alternatives you've considered How it can be done it existing Terraform api For provider need to create new command e.g: accept
It will work in next chain of commands:
- terraform -export - to pull remote changes
- terraform plan -out=tfplan -no-color
- detect changes something like with saving resources IDs: terraform show -no-color tfplan | grep -E '^+ |^- |~ '
- for each: terraform state rm 'resource_id'
- for each: terraform import 'resource_id' now we have a state like in SaaS Dynatrace without back push
As alternative:
possible to make direct changes in state file:
Pseudo code:
Additional context A similar problem discussed in the community but ignore changes will not solve the problem of Dynatrace top-down creation approach. https://itnext.io/how-and-when-to-ignore-lifecycle-changes-in-terraform-ed5bfb46e7ae
Any discusssion or ideas are welkome)