-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about generated routing table #17
Comments
Hey Ilene, I believe this is just a vestige from the original, we no longer have that section in the HA version. |
Thanks @Joel-Cripps . I think this terraform still backs the single instance IBM catalog offering - I assume it's still ok to use, even though the HA is there as well? |
Yes of course. HA is a separate repo. If you are looking for a CLI/local based terraform deploy you can check out our other repos here: https://github.com/fortinet/fortigate-terraform-deploy/tree/main/ibm |
Ah ok, thanks for the link - I may switch over. I'm incorporating the terraform into a larger 'landing zone'. I've forked this repository (https://github.com/ibmcloud-tech-canada/ibm-fortigate-terraform-deploy) and made some updates, like ensuring all resources land in a resource group, and I have another update coming that takes a customer provided key to encrypt the boot and data volumes. I also had to remove the provider block to use as a module in a larger script. |
Sounds good. PR's are welcome if you want to send some of the changes this way. Otherwise when you have finished send us the link and maybe we can incorporate some of the changes. Customer provided keys to encrypt would be a useful addition for sure. |
I notice that a routing table is created in vpc.tf, but it's not bound to any subnets and doesn't have any rules. What is the intended purpose of this routing table?
The text was updated successfully, but these errors were encountered: