Skip to content

Deprecated argument in scaleway_instance_security_group_rules used in documentation #3106

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

Open
alexmge opened this issue May 23, 2025 · 0 comments
Labels
registry Managed Container Registry issues, bugs and feature requests

Comments

@alexmge
Copy link

alexmge commented May 23, 2025

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Affected Resource(s)

  • scaleway_instance_security_group_rules
  • scaleway_instance_security_group

About

The ip argument of the scaleway_instance_security_group_rules resource is used multiple times in the documentation at :

Even though it has been marked as deprecated in #1460 in favor of ip_range, leading to a deprecated warning in the official linter extension for VSCode if you use it. Exact line here.

However it's not even marked as deprecated in the documentation of the resource itself : https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/instance_security_group_rules#ip-1.

So what's going on here ? Is ip even deprecated or not ?

References

@jremy42 jremy42 added the registry Managed Container Registry issues, bugs and feature requests label May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
registry Managed Container Registry issues, bugs and feature requests
Projects
None yet
Development

No branches or pull requests

2 participants