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

New Resource: azurerm_dev_center_network_connection #26718

Merged
merged 11 commits into from
Aug 1, 2024

Conversation

neil-yechenwei
Copy link
Contributor

@neil-yechenwei neil-yechenwei commented Jul 22, 2024

Community Note

  • Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

This PR is to support new resource Dev Center Network Connection.

API Spec: https://github.com/Azure/azure-rest-api-specs/blob/09741dc7c9e43a8f9401d782186cac723dc4af71/specification/devcenter/resource-manager/Microsoft.DevCenter/stable/2023-04-01/vdi.json#L707

Overview: https://learn.microsoft.com/en-us/azure/dev-box/how-to-configure-network-connections?tabs=AzureADJoin

PR Checklist

  • I have followed the guidelines in our Contributing Documentation.
  • I have checked to ensure there aren't other open Pull Requests for the same update/change.
  • I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
  • I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
  • I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
    For example: “resource_name_here - description of change e.g. adding property new_property_name_here

Changes to existing Resource / Data Source

  • I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
  • I have written new tests for my resource or datasource changes & updated any relevent documentation.
  • I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
  • (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

  • My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)
--- PASS: TestAccDevCenterNetworkConnection_basic (788.66s)
--- PASS: TestAccDevCenterNetworkConnection_requiresImport (721.97s)
--- PASS: TestAccDevCenterNetworkConnection_complete (1301.52s)
--- PASS: TestAccDevCenterNetworkConnection_update (1595.60s)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

  • New Resource: azurerm_dev_center_network_connection

This is a (please select all that apply):

  • Bug Fix
  • New Feature (ie adding a service, resource, or data source)
  • Enhancement
  • Breaking Change

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

Copy link
Contributor

@ms-zhenhua ms-zhenhua left a comment

Choose a reason for hiding this comment

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

Hi @neil-yechenwei, Thanks for this PR - I've taken a look through and left some comments inline. If we can fix those up, this should be good to go 👍

@neil-yechenwei
Copy link
Contributor Author

@ms-zhenhua , Thanks for the comments. I updated PR. Please take another look. Thanks.

Copy link
Contributor

@ms-zhenhua ms-zhenhua left a comment

Choose a reason for hiding this comment

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

@neil-yechenwei, thank you for your updates. LGTM~

ms-zhenhua

This comment was marked as duplicate.

@neil-yechenwei neil-yechenwei marked this pull request as ready for review July 30, 2024 02:10
Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

Thanks @neil-yechenwei. Overall this is looking good, once you've fixed up the few minor comments then this will be good to go!

Comment on lines 202 to 216
if v := props.SubnetId; v != nil {
state.SubnetId = pointer.From(v)
}

if v := props.DomainName; v != nil {
state.DomainName = pointer.From(v)
}

if v := props.DomainUsername; v != nil {
state.DomainUsername = pointer.From(v)
}

if v := props.OrganizationUnit; v != nil {
state.OrganizationUnit = pointer.From(v)
}
Copy link
Member

Choose a reason for hiding this comment

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

pointer.From can handle the nil check for us so these can be simplified

Suggested change
if v := props.SubnetId; v != nil {
state.SubnetId = pointer.From(v)
}
if v := props.DomainName; v != nil {
state.DomainName = pointer.From(v)
}
if v := props.DomainUsername; v != nil {
state.DomainUsername = pointer.From(v)
}
if v := props.OrganizationUnit; v != nil {
state.OrganizationUnit = pointer.From(v)
}
state.SubnetId = pointer.From(props.SubnetId)
state.DomainName = pointer.From(props.DomainName)
state.DomainUsername = pointer.From(props.DomainUsername)
state.OrganizationUnit = pointer.From(props.OrganizationUnit)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Comment on lines 230 to 232
lifecycle {
ignore_changes = [subnet]
}
Copy link
Member

Choose a reason for hiding this comment

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

This change has been reverted so we should remove this

Suggested change
lifecycle {
ignore_changes = [subnet]
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Comment on lines 27 to 29
lifecycle {
ignore_changes = [subnet]
}
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
lifecycle {
ignore_changes = [subnet]
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@neil-yechenwei
Copy link
Contributor Author

@stephybun , thanks for the comments. I updated PR. Below is the latest test result I just now triggered.

image
image
image
image

Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

Thanks @neil-yechenwei LGTM 💯

@stephybun stephybun merged commit 4b2649c into hashicorp:main Aug 1, 2024
37 checks passed
@github-actions github-actions bot added this to the v3.114.0 milestone Aug 1, 2024
stephybun added a commit that referenced this pull request Aug 1, 2024
Copy link

github-actions bot commented Sep 3, 2024

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 Sep 3, 2024
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.

3 participants