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

"azurerm_spring_cloud_service" - supports property "required_network_traffic_rules" #11633

Merged
merged 3 commits into from
May 18, 2021

Conversation

njuCZ
Copy link
Contributor

@njuCZ njuCZ commented May 8, 2021

this is a readonly property.

It lists the required traffic in virtual network mode.

some users want to limit spring cloud app's traffic, the "required_traffic" tells users which traffic must be enabled.

image

@@ -158,6 +158,22 @@ The following attributes are exported:

* `outbound_public_ip_addresses` - A list of the outbound Public IP Addresses used by this Spring Cloud Service.

* `required_traffic` - A list of `required_traffic` blocks as defined below.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does required traffic mean? is there a better more clear name for this property?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

according to the service team's explanation, some users want to limit the traffic of spring cloud app, but when spring cloud service is integrated with virtual network, there are some essential network trafiic that must be enabled. Users could put these into white list or firewall rules.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so these are firewall_required_access_rules? or firewall_required_access?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @katbyte , the reason why we don't want to put "firewall" keyword in this property, is that Azure offers another service "network security group" which basically could do the similar job of allowing/denying traffic, and many customers are using it to secure their network. We don't want to have the "firewall" keyword in property name, which might be potentially misleading. Thanks.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case I think the current name required_traffic is a better fit than required_access since:

  1. those are network configuration, not authorization
  2. the name aligns our API/SDK and will reduce confusion.
    @katbyte what do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

required_traffic is rather vague and is confusing, if it can be used elsewhere then maybe it should be required_network_access or even required_network so it reads like required_network.port

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

required_network.direction looked strange to me so how about required_traffic_rules?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

your not wrong, i think its traffic without a qualifier that stands out to me, split the difference with required_network_traffic_rules? 🙃

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok let move forward with that name

@ghost ghost added size/L and removed size/M labels May 18, 2021
@njuCZ njuCZ changed the title "azurerm_spring_cloud_service" - supports property "required_traffic" "azurerm_spring_cloud_service" - supports property "required_network_traffic_rules" May 18, 2021
@njuCZ
Copy link
Contributor Author

njuCZ commented May 18, 2021

@katbyte thanks for your suggestion, I have renamed to required_network_traffic_rules. please have a look again

@ghost ghost removed the waiting-response label May 18, 2021
@njuCZ njuCZ requested a review from katbyte May 18, 2021 05:14
@katbyte katbyte added this to the v2.60.0 milestone May 18, 2021
Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thaks @njuCZ - LGTM 👍

@katbyte katbyte merged commit 8daf2f9 into hashicorp:master May 18, 2021
katbyte added a commit that referenced this pull request May 18, 2021
@ghost
Copy link

ghost commented May 21, 2021

This has been released in version 2.60.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.60.0"
}
# ... other configuration ...

favoretti pushed a commit to gro1m/terraform-provider-azurerm that referenced this pull request May 26, 2021
…traffic_rules" (hashicorp#11633)

* "azurerm_spring_cloud_service" - supports property "required_traffic"

* update

* renamed to `required_network_traffic_rules`
favoretti pushed a commit to gro1m/terraform-provider-azurerm that referenced this pull request May 26, 2021
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants