Skip to content

New Data Source: azurerm_dev_center_project#29747

Merged
sreallymatt merged 2 commits intohashicorp:mainfrom
neil-yechenwei:devcenterprojectdatasource
May 30, 2025
Merged

New Data Source: azurerm_dev_center_project#29747
sreallymatt merged 2 commits intohashicorp:mainfrom
neil-yechenwei:devcenterprojectdatasource

Conversation

@neil-yechenwei
Copy link
Contributor

@neil-yechenwei neil-yechenwei commented May 29, 2025

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

Added new data source azurerm_dev_center_project for #29648

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 relevant 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: TestAccDevCenterProjectDataSource_basic (960.60s)

Change Log

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

  • New Data Source: azurerm_dev_center_project

This is a (please select all that apply):

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

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the provider.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Note

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

Copy link
Collaborator

@sreallymatt sreallymatt 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, I've left 2 minor suggestions inline


* `description` - The description of the Dev Center Project.

* `dev_center_id` - The ID of an associated DevCenter.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
* `dev_center_id` - The ID of an associated DevCenter.
* `dev_center_id` - The ID of the associated Dev Center.

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


* `location` - The Azure Region where the Dev Center Project exists.

* `maximum_dev_boxes_per_user` - When specified, limits the maximum number of Dev Boxes a single user can create across all pools in the project.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
* `maximum_dev_boxes_per_user` - When specified, limits the maximum number of Dev Boxes a single user can create across all pools in the project.
* `maximum_dev_boxes_per_user` - The maximum number of Dev Boxes a single user can create across all pools in the project.

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

@sreallymatt , thanks for the comments. I updated PR. Please take another look.

Copy link
Collaborator

@sreallymatt sreallymatt 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!

@sreallymatt sreallymatt merged commit 93774e0 into hashicorp:main May 30, 2025
35 checks passed
@github-actions github-actions bot added this to the v4.32.0 milestone May 30, 2025
sreallymatt added a commit that referenced this pull request May 30, 2025
wyattfry pushed a commit that referenced this pull request Jun 5, 2025
@github-actions
Copy link
Contributor

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 30, 2025
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.

2 participants