v2ray-core VS terraform-provider-azurerm

Hey there! Lots of experience with this having lived in China for 2 years. I recommend you look into xray-core or v2ray.

https://github.com/v2fly/v2ray-core

https://github.com/XTLS/Xray-core

Here are my configs: https://github.com/acheong08/notes/tree/main/xray

cd ~ wget https://github.com/v2fly/v2ray-core/releases/download/v5.7.0/v2ray-linux-64.zip sudo apt install -y unzip unzip v2ray-linux-64.zip cp geoip/output/dat/* . ./v2ray uuid

If the changing por trick work you can try shadowsocks or v2ray.

Normal VPNs that you can see ads all over the place like N*rdVPN won't work, period. The correct way is to rent a few servers from different providers, make sure their ips are not blocked, and build your own V2Ray or Trojan service first. The Chinese gov will not be able to distinguish your Trojan traffic from ordinary https traffic, so the only thing that's sus to them would be the fact that all your traffic goes to one foreign ip, but I've been doing it for a few years without officials knocking on my door so yeah I think it will work for you as well. I don't take responsibility tho, do your research.

Given that every other client is mostly using https://github.com/v2fly/v2ray-core that can be compiled for every architecture/platform that Outline client supports, maybe it's worth investing time into allowing it as a backend. It can even be used for pure shadowsocks since it's for sure more updated than the old golang shadowsocks implementation.

v2Ray: https://v2fly.org

So this is doing my head in. Related to https://github.com/hashicorp/terraform-provider-azurerm/issues/6117

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

Yeah we imported all the related resources. I could now find an issue, which exactly describes our problem. Unfortunately it is open since 2020: https://github.com/hashicorp/terraform-provider-azurerm/issues/8794

Like other people said, use the azurerm provider docs, they're pretty good. But that's where knowing Azure comes in handy because you'll have to figure out what TF resource to use to accomplish a given goal.

It’s not difficult at all syntactically. But you must understand the provider you are automating. So your azure knowledge is key in this case. Read the Azure provider docs and you will be easily able to put something together. https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs