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

Handle nil values for AllowBlobPublicAccess #12689

Merged
merged 6 commits into from
Aug 31, 2021

Conversation

koikonom
Copy link
Contributor

No description provided.

@koikonom koikonom requested a review from a team July 22, 2021 09:52
@koikonom koikonom added this to the v2.69.0 milestone Jul 22, 2021
@katbyte katbyte modified the milestones: v2.69.0, v2.70.0 Jul 23, 2021
Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

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

hey @koikonom

Thanks for this PR.

I've taken a look through and on the whole this LGTM, but I think we should consider renaming this field in 3.0 too, so that it's explicit what it does (since this is a source of confusion right now)?

Thanks!

if props.AllowBlobPublicAccess != nil {
allowBlobPublicAccess = *props.AllowBlobPublicAccess
}
d.Set("allow_blob_public_access", allowBlobPublicAccess)
Copy link
Contributor

Choose a reason for hiding this comment

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

I still think we need to rename this field in 3.0 to something more descriptive because it's confusing and doesn't accurately describe what it does (which is that nested items within this Account [e.g. Containers Blobs etc] can opt into being public) - maybe can_nested_items_be_public or something? The benefit of doing that is the Deprecated argument here would allow us to explain what this field actually does?

Copy link
Collaborator

Choose a reason for hiding this comment

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

maybe "public_nested_items_enabled"

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 that suffers from the same issue, I think we'll need to be a little wordy to be clear here tbh, given how this is misleading at the moment?

Copy link

Choose a reason for hiding this comment

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

what about allow_public_nested_items ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

After further discussion with @tombuildsstuff and @redeux we decided to go with allow_nested_items_to_be_public.

Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

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

A few minor comments but this otherwise LGTM 👍

@koikonom koikonom force-pushed the b/handle_nil_publicaccess_flag branch from 40072eb to a7f32bb Compare August 25, 2021 10:51
@koikonom
Copy link
Contributor Author

Rebased to address conflicts.

@katbyte katbyte modified the milestones: v2.74.0, v2.75.0 Aug 27, 2021
Copy link
Contributor

@manicminer manicminer left a comment

Choose a reason for hiding this comment

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

LGTM 🕺

@koikonom koikonom merged commit f60e08b into main Aug 31, 2021
@koikonom koikonom deleted the b/handle_nil_publicaccess_flag branch August 31, 2021 16:32
koikonom pushed a commit that referenced this pull request Aug 31, 2021
@github-actions
Copy link

github-actions bot commented Sep 2, 2021

This functionality has been released in v2.75.0 of the Terraform 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!

@github-actions
Copy link

github-actions bot commented Oct 3, 2021

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 Oct 3, 2021
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.

5 participants