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]: DataZone Glossary #38602

Merged
merged 11 commits into from
Aug 1, 2024
Merged

Conversation

ThomasZalewski
Copy link
Contributor

Description

This resource will allow practitioners to create DataZone Glossary for a DataZone Domain via Terraform.

Relations

Relates #37423

References

Output from Acceptance Testing

% make testacc TESTS=TestAccDataZoneGlossary PKG=datazone
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.5 test ./internal/service/datazone/... -v -count 1 -parallel 20 -run='TestAccDataZoneGlossary'  -timeout 360m
=== RUN   TestAccDataZoneGlossary_basic
=== PAUSE TestAccDataZoneGlossary_basic
=== RUN   TestAccDataZoneGlossary_update
=== PAUSE TestAccDataZoneGlossary_update
=== RUN   TestAccDataZoneGlossary_disappears
=== PAUSE TestAccDataZoneGlossary_disappears
=== CONT  TestAccDataZoneGlossary_basic
=== CONT  TestAccDataZoneGlossary_disappears
=== CONT  TestAccDataZoneGlossary_update
--- PASS: TestAccDataZoneGlossary_disappears (27.28s)
--- PASS: TestAccDataZoneGlossary_basic (28.41s)
--- PASS: TestAccDataZoneGlossary_update (38.86s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/datazone   44.480s

@ThomasZalewski ThomasZalewski requested a review from a team as a code owner July 30, 2024 19:23
Copy link

Community Note

Voting for Prioritization

  • Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

For Submitters

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions github-actions bot added documentation Introduces or discusses updates to documentation. 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. prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. labels Jul 30, 2024
if resp.Diagnostics.HasError() {
return
}
in.DomainIdentifier = plan.DomainId.ValueStringPointer()
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should name the input value to match what AWS has named it. In the event that the API changes it minimizes the possibility of collisions

return
}

if !plan.Description.Equal(state.Description) || !plan.Name.Equal(state.Name) || !plan.Description.Equal(state.Description) {
Copy link
Contributor

Choose a reason for hiding this comment

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

plan.Description.Equal(state.Description) is repeated in this condition

Comment on lines 286 to 289




Copy link
Contributor

Choose a reason for hiding this comment

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

cleanup spacing

Co-authored-by: Adrian Johnson <adrian.johnson@hashicorp.com>
Copy link

github-actions bot commented Aug 1, 2024

Thank you for your contribution! 🚀

A new usage of AWS SDK for Go V1 was detected. Please prefer AWS SDK for Go V2 for all net-new services. If this is an enhancement or bug fix to an existing AWS SDK Go V1 based resource, this comment can be safely ignored.

For additional information refer to the AWS SDK for Go Versions page in the contributor guide.



resource "aws_datazone_glossary" "test" {
client_token = "example_token"
Copy link
Contributor

Choose a reason for hiding this comment

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

client_token should be set on the request by the provider. It should not be mentioned as an input value


The following arguments are required:

* `client_token` - (Required) Unique case-sensitive identifier that is provided to ensure the idempotency of the request. Must follow regex pattern of ^[\x21-\x7E]+$ and have length between 1 and 128.
Copy link
Contributor

Choose a reason for hiding this comment

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

^ similar to previous comment

Copy link
Contributor

@johnsonaj johnsonaj left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

% make testacc TESTS=TestAccDataZoneGlossary PKG=datazone

make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.5 test ./internal/service/datazone/... -v -count 1 -parallel 20 -run='TestAccDataZoneGlossary'  -timeout 360m
=== RUN   TestAccDataZoneGlossary_basic
=== PAUSE TestAccDataZoneGlossary_basic
=== RUN   TestAccDataZoneGlossary_update
=== PAUSE TestAccDataZoneGlossary_update
=== RUN   TestAccDataZoneGlossary_disappears
=== PAUSE TestAccDataZoneGlossary_disappears
=== CONT  TestAccDataZoneGlossary_basic
=== CONT  TestAccDataZoneGlossary_disappears
=== CONT  TestAccDataZoneGlossary_update
--- PASS: TestAccDataZoneGlossary_basic (27.48s)
--- PASS: TestAccDataZoneGlossary_disappears (30.31s)
--- PASS: TestAccDataZoneGlossary_update (44.13s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/datazone	50.175s

@ThomasZalewski ThomasZalewski merged commit 220214f into main Aug 1, 2024
42 checks passed
@ThomasZalewski ThomasZalewski deleted the f/datazone-glossary-resource branch August 1, 2024 20:43
@github-actions github-actions bot added this to the v5.61.0 milestone Aug 1, 2024
@github-actions github-actions bot removed the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Aug 2, 2024
Copy link

github-actions bot commented Aug 2, 2024

This functionality has been released in v5.61.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

github-actions bot commented Sep 1, 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 issues.
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 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. generators Relates to code generators. service/datazone Issues and PRs that pertain to the datazone service. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants