Added comments about github and 3rd-party providers. #492
Conversation
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
1 similar comment
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
Vercel Previews Deployed
|
Broken Link CheckerNo broken links found! 🎉 |
| @@ -69,3 +69,5 @@ Additionally, the agent must also be able to communicate with any services requi | |||
| | releases.hashicorp.com | tcp/443, HTTPS | Outbound | Updating agent components and downloading Terraform binaries | | |||
| | archivist.terraform.io | tcp/443, HTTPS | Outbound | Blob Storage | | |||
| | agents.terraform.io | tcp/7146, TCP | Outbound | Agent RPC interface (currently used for request forwarding only) | | |||
|
|
|||
| Additionally, outbound traffic to *.github.com should be allowed if any 3rd-party providers are used. These can be pulled in implicitly by resource definitions, or explicitly by provider configurations added to the HCL code. | |||
There was a problem hiding this comment.
@henryk-rychlik Could you add this to the table above? I feel like it'd make sense with everything above! Something like this:
| github.com | ? | Outbound | Required if you are using a 3rd party provider while defining resources or in configuring providers. |
I'm not sure what the prot/protocal would be though?
This wasn't explicitly spelled out previously. Only implied by the following sentence: