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

aws_s3_bucket: Remove optional from arn and hosted_zone_id #27597

Merged
merged 1 commit into from
Nov 4, 2022

Conversation

cgetzen
Copy link
Contributor

@cgetzen cgetzen commented Nov 2, 2022

Description

Currently, the arn and hosted_zone_id attributes are marked as optional, hinting that they can be set within a resource block (as opposed to being solely computed attributes).

However, arn and hosted_zone_id should never be set with user-generated values. arn is derived from other attributes, and hosted_zone_id is looked up here.

Relations

n/a

References

https://discuss.hashicorp.com/t/providers-schema-how-to-distinguish-attributes-from-arguments/5029/3

Output from Acceptance Testing

$ make testacc TESTS=TestAccXXX PKG=ec2

...

@github-actions github-actions bot added size/XS Managed by automation to categorize the size of a PR. service/s3 Issues and PRs that pertain to the s3 service. needs-triage Waiting for first response or review from a maintainer. labels Nov 2, 2022
@github-actions
Copy link

github-actions bot commented Nov 2, 2022

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
Copy link

github-actions bot commented Nov 2, 2022

Hey @cgetzen 👋 Thank you very much for your contribution! At times, our maintainers need to make direct edits to pull requests in order to help get it ready to be merged. Your current settings do not allow maintainers to make such edits. To help facilitate this, update your pull request to allow such edits as described in GitHub's Allowing changes to a pull request branch created from a fork documentation. (If you're using a fork owned by an organization, your organization may not allow you to change this setting. If that is the case, let us know.)

@cgetzen
Copy link
Contributor Author

cgetzen commented Nov 2, 2022

This PR is from a github organization.

Who can use this feature
People with push access to the upstream repository of a fork owned by a personal account can commit to the forked branches.

It looks like I can only allow changes from personal account fork.
I'm happy to recreate the PR on a personal fork, or apply feedback from maintainers to this PR.

@justinretzolk justinretzolk added enhancement Requests to existing resources that expand the functionality or scope. and removed needs-triage Waiting for first response or review from a maintainer. labels Nov 2, 2022
@gdavison gdavison added breaking-change Introduces a breaking change in current functionality; usually deferred to the next major release. bug Addresses a defect in current functionality. and removed enhancement Requests to existing resources that expand the functionality or scope. labels Nov 4, 2022
Copy link
Contributor

@gdavison gdavison left a comment

Choose a reason for hiding this comment

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

Great catch, @cgetzen! That's been there for a long time

@gdavison gdavison merged commit 31ec5d1 into hashicorp:main Nov 4, 2022
@github-actions github-actions bot added this to the v4.39.0 milestone Nov 4, 2022
gdavison added a commit that referenced this pull request Nov 4, 2022
@github-actions
Copy link

This functionality has been released in v4.39.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!

@apmovamo
Copy link

apmovamo commented Nov 14, 2022

I think the Documentation about the AWS S3 bucket should be changed. It still shows for the last terraform version that the hosted_zone_id is an attribute.

@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 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 Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking-change Introduces a breaking change in current functionality; usually deferred to the next major release. bug Addresses a defect in current functionality. service/s3 Issues and PRs that pertain to the s3 service. size/XS Managed by automation to categorize the size of a PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants