Skip to content
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

[FEATURE] Allow "civo_network" to specify the nameserver and cidr #202

Closed
mrsimonemms opened this issue Apr 16, 2024 · 7 comments
Closed

Comments

@mrsimonemms
Copy link

Description

The Civo CLI allows a network to be created with both --cidr-v4 and --nameservers-v4 specified. This doesn't appear to be possible with Terrform.

  1. Am I missing something and is it already possible to do with Terraform?
  2. If not, can we have some way of doing this with TF please?

Screenshots

No response

Additional information

No response

@uzaxirr
Copy link
Member

uzaxirr commented Apr 18, 2024

Hey,
from what i see is that CIDR and Nameserver is already been implemented in the network resource.
https://github.com/civo/terraform-provider-civo/blob/master/civo/network/resource_network.go#L33

You can use the fields cidr_v4 and nameservers_v4 in your network block.
Let me know if this resolves your query.

@mrsimonemms
Copy link
Author

Yes, you're right. It doesn't solve the problem of use in Terraform though - this feature was only done ~3 weeks ago, but the latest (1.0.39) release was done in October.

I guess a new release should solve that problem. Any idea when the next release is scheduled?

@mertcangokgoz
Copy link

I'm waiting for the new version to arrive. 👍🏻 especially this one

@mrsimonemms
Copy link
Author

@uzaxirr what's the policy/release schedule? Anything I can do to help expedite this?

@mertcangokgoz
Copy link

Anything? @uzaxirr

@uzaxirr
Copy link
Member

uzaxirr commented Apr 29, 2024

Here you go everyone: https://github.com/civo/terraform-provider-civo/releases/tag/v1.0.40

@uzaxirr
Copy link
Member

uzaxirr commented Apr 29, 2024

Closing this issue wrt: #200

@uzaxirr uzaxirr closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants