Mohammad Alhomaid
Mohammad Alhomaid
Thank you @rajaramanlala, I have used `oci_core_drg_attachment_management` but I tried to import it I got the following error ``` terraform import module.env.module.fast_connect.oci_core_drg_attachment_management.x_drg_attachment_virtual_circuit ocid1.drgattachment.oc1.me-jeddah-1.x Acquiring state lock. This may take a...
@rajaramanlala Do you mean terraform config? if that's so, I tried both before importing the resource providing `compartment_id`, and without it, I think the issue is for some reason, OCI...
Again same issue with different attachment type ``` resource "oci_core_drg_attachment_management" "y_drg_attachment_ipsec_2" { drg_id = oci_core_drg.y_drg.id compartment_id = oci_identity_compartment.main.id display_name = "DRG Attachment for IPSec Tunnel: ipsectunnel20220127070422-2" attachment_type = "IPSEC_TUNNEL" network_details...
> I have tried and it gives me the following error: > > ``` > org.apache.spark.SparkUnsupportedOperationException: Data source bigquery does not support streamed writing. > at org.apache.spark.sql.errors.QueryExecutionErrors$.streamedOperatorUnsupportedByDataSourceError(QueryExecutionErrors.scala:696) > at org.apache.spark.sql.execution.datasources.DataSource.createSink(DataSource.scala:326)...
I worked around it by using `writeStream.foreachBatch` ``` def write_to_bigquery(batch_df, batch_id): batch_df.write.format('bigquery') \ .option("table", "") \ .option("temporaryGcsBucket", "") \ .option("checkpointLocation", "") \ .option("writeMethod", "direct") \ .save() df.writeStream \ .foreachBatch(write_to_bigquery) \...
It would be great, I don't know how homebridge handles it but it seems like it should be a security accessory to be shown as lock, and AFAIK it would...
But this actually doesn't work for querying normal users repos(not orgs)
> But this actually doesn't work for querying normal users repos(not orgs) Any suggestion on which approach should we use since both approaches are not covering all use cases?
@mlibbey It worked I added it to both client and origin like this `map https://example.com:443 https://example.com:443` Thank you so much! @mlibbey I don't know why it was working with more...
@mlibbey with me curl and other clients are working without any special config