randr97 edited a comment on issue #8890: URL: https://github.com/apache/airflow/issues/8890#issuecomment-629808815
> @randr97 a lot of organizations manage infrastructure like S3 buckets through infrastructure-as-code scripts, usually Terraform since that is what AWS supports natively. The way Terraform works is that it maintains the state of all infrastructure in a backend (usually remote). Let's say someone configured an s3 bucket and deployed it using Terraform, if your DAG then deletes that bucket, it will create a mismatch between the Terraform state and the reality of the deployment (TF state will presume the bucket exists when in fact it doesn't). > > I still think this is a useful feature, but I am wondering if there is a way for the operator to accept a flag that somehow communicates to a TF backend in case a bucket is deleted. > > Also keep in mind that your create bucket operator should have all the required configuration options for IAM roles, ACL permissions etc. Oh now I get the issue. So there should be a mechanism where airflow could talk to TF backend so that for eg if some keys have to be created via terraform and dag deletes the bucket it should technically fail! Would be great if we could discuss this in detail on slack?? ---------------------------------------------------------------- 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: us...@infra.apache.org
