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

[BUG] civo_network resource using the word label incorrectly #227

Open
fernando-villalba opened this issue Jun 19, 2024 · 1 comment · May be fixed by #231
Open

[BUG] civo_network resource using the word label incorrectly #227

fernando-villalba opened this issue Jun 19, 2024 · 1 comment · May be fixed by #231
Assignees
Labels
bug Something isn't working

Comments

@fernando-villalba
Copy link
Contributor

Description

The civo_network resource takes exactly one parameter called label to name it.

This parameter should be called name as this is not exactly a label.

This is also a problem if in the future we add the ability to add labels to the network

resource "civo_network" "test-issue" {
    label = "test-something"
}

One of the outputs for the network is called name, we need to change that to be the actual name as the input of the user, the current output name that this is giving is incorrect and not useful for anything

Acceptance criteria

  • Change label to name
  • Change the output of the name to be the actual name of the network (same as the input).
  • Keep label input temporarily but mark it as obsolete, to be removed in a future version.

Screenshots

No response

Additional information

No response

@fernando-villalba fernando-villalba added the bug Something isn't working label Jun 19, 2024
@uzaxirr uzaxirr self-assigned this Jun 19, 2024
@uzaxirr uzaxirr linked a pull request Jun 19, 2024 that will close this issue
@uzaxirr
Copy link
Member

uzaxirr commented Jun 22, 2024

This is an API dependent issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants