[GitHub] [airflow] jaketf commented on issue #10550: Terraform provider based on Stable API

[GitBox <gi...@apache.org>]

jaketf commented on issue #10550:
URL: https://github.com/apache/airflow/issues/10550#issuecomment-680150041


   I could see use cases for the following (in decreasing order of how likely I'd be to recommend managing in terraform):
   1. Pool: this feels rather infrastructure level could be something naturally in terraform's realm
   1. Variable: add / update a references to infra provisioned by terraform that will be referenced by DAGs
   1. Connection: add connection for db provisioned by terraform (though this seems worse than using secrets backend)
   1. TriggerDagRun: this is more dubious but perhaps there is a scenario where after provisioning a bunch of infrastructure there is need to kick off an airflow DAG.
   
   I think providing resources / data sources for other resources in the API would likely encourage pretty dangerous patterns leading to unpredictable terraform applies. Keep in mind that terraform likes to be authoritative about things so any values we expect to drift will be confusing to terraform and it will try to correct this drift. 
   
   Personally I'd be more interested in use cases for the "opposite" integration (airflow running terraform https://github.com/apache/airflow/issues/10454)
   
   It is good to give users options as there are many different organization that may have different needs / opinions.
   
   I've worked on [terraform-cdap-provider](https://github.com/GoogleCloudPlatform/terraform-provider-cdap#:~:text=Terraform%20CDAP%20Provider,official%20Google%20or%20Hashicorp%20product) in the past which we basically implemented by hand. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org