Skip to content

[New Resource] DataZone - Associate Environment Role #44411

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

[New Resource] DataZone - Associate Environment Role #44411

wants to merge 5 commits into from
+588 −2

Conversation

AlejandroJL
Copy link

@AlejandroJL AlejandroJL commented Sep 23, 2025 •
edited
Loading

Description

This resource will allow practitioners to create Associate Environment Role for DataZone via Terraform.

References

https://docs.aws.amazon.com/datazone/latest/APIReference/API_AssociateEnvironmentRole.html
https://docs.aws.amazon.com/datazone/latest/APIReference/API_DisassociateEnvironmentRole.html

Output from Acceptance Testing

% make testacc TESTS=TestAccAssociateEnvironmentRole_basic PKG=datazone

Relations

Closes #44413

@AlejandroJL
Add new resource
f9dcaff
@AlejandroJL
Remove the profile_identifier field as a requirement, as it is not
b06001d 
mandatory and is necessary to create a CustomAwsService environment
@AlejandroJL AlejandroJL requested a review from a team as a code owner September 23, 2025 06:40
@github-actions GitHub Actions
Copy link
Contributor

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

  • Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
  • Please see our prioritization guide for additional information on how the maintainers handle prioritization.
  • Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Sep 23, 2025 •
edited
Loading

⚠️ Our automation has detected the following potential issues with your pull request

❌ Unnecessary Changelog Changes (Click to expand)

The CHANGELOG.md file contents are handled by the maintainers during merge. This is to prevent pull request merge conflicts, especially for contributions which may not be merged immediately. Please see the Changelog Process section of the contributing guide for additional information.

Remove any changes to the CHANGELOG.md file and commit them in this pull request to prevent delays with reviewing and potentially merging it.

❌ Changelog Entry Required (Click to expand)

The proposed change requires a changelog entry. Please see the Changelog Process section of the contributing guide for information on the changelog generation process.

Tip: This check is not triggered for draft pull requests, since the pull request number is not known until the pull request is opened and is required to create a changelog entry. Opening a pull request first as a draft, adding the requisite changelog entry file, and then marking the pull request as ready for review will prevent future warnings.

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. generators Relates to code generators. service/datazone Issues and PRs that pertain to the datazone service. size/XL Managed by automation to categorize the size of a PR. labels Sep 23, 2025
@AlejandroJL AlejandroJL mentioned this pull request Sep 23, 2025
Open
@github-actions github-actions bot added documentation Introduces or discusses updates to documentation. provider Pertains to the provider itself, rather than any interaction with AWS. labels Sep 23, 2025
@justinretzolk justinretzolk added new-resource Introduces a new resource. and removed needs-triage Waiting for first response or review from a maintainer. labels Sep 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
documentation Introduces or discusses updates to documentation. generators Relates to code generators. new-resource Introduces a new resource. provider Pertains to the provider itself, rather than any interaction with AWS. service/datazone Issues and PRs that pertain to the datazone service. size/XL Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[New Resource] DataZone - Associate Environment Role
2 participants
@AlejandroJL @justinretzolk