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

chore(master): release 4.0.0 #214

Merged
merged 2 commits into from
Apr 11, 2023
Merged

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Jan 13, 2023

🤖 I have created a release beep boop

4.0.0 (2023-04-06)

⚠ BREAKING CHANGES

  • add support for custom_placement_config (#231)
  • TPG >= 4.42: add support for public_access_prevention (#218)
  • location inverse control in bucket name prefix (#186)
  • Add matches_prefix and matches_suffix conditions (#202)

Features

  • Add matches_prefix and matches_suffix conditions (#202) (8db2eb3)
  • add support for custom_placement_config (#231) (a0bbdbd)
  • Hmac access (#181) (e5e4909)
  • location inverse control in bucket name prefix (#186) (dbd3c35)
  • TPG >= 4.42: add support for public_access_prevention (#218) (4469954)

This PR was generated with Release Please. See documentation.

@release-please release-please bot requested a review from a team as a code owner January 13, 2023 20:05
@release-please release-please bot force-pushed the release-please--branches--master branch 3 times, most recently from 95e0308 to cd3787c Compare January 23, 2023 16:38
@release-please release-please bot force-pushed the release-please--branches--master branch from cd3787c to aaacd7b Compare February 2, 2023 19:13
@comment-bot-dev
Copy link

@release-please[bot]
Thanks for the PR! 🚀
✅ Lint checks have passed.

@lhriley
Copy link

lhriley commented Feb 3, 2023

I ran into some state issues related to the provider upgrade. To fix it I had to edit state manually, so I came up with a little bashism to do it for me (requires ~jq-1.6):

Terraform

terraform state pull | sed "s/bucket_policy_only/uniform_bucket_level_access/g" | jq -M '.serial = (.serial + 1)' | jq -M 'del (.resources[].instances[].attributes["b64"])' | terraform state push -

Terragrunt:

terragrunt state pull | sed "s/bucket_policy_only/uniform_bucket_level_access/g" | jq -M '.serial = (.serial + 1)' | jq -M 'del (.resources[].instances[].attributes["b64"])' | terragrunt state push -

You might add this to the changelog or README.md to help people avoid issues upgrading.

@release-please release-please bot force-pushed the release-please--branches--master branch 2 times, most recently from d318847 to b2a41fb Compare February 9, 2023 23:06
@dpebot
Copy link
Collaborator

dpebot commented Feb 9, 2023

/gcbrun

@nhuray
Copy link

nhuray commented Feb 14, 2023

@lhriley What's missing to release that version ?

I would like to use it in order to not have the GCP region into the bucket name !

@lhriley
Copy link

lhriley commented Feb 14, 2023

@lhriley What's missing to release that version ?

I would like to use it in order to not have the GCP region into the bucket name !

The problem I had was a jump in a major version of Google and hashicorp providers that causes a breaking state change. This happened because of the change to the minimum version of the Google provider. The commands I shared fixed the state for me and now I'm running the pre-release without any apparent issues.

@release-please release-please bot force-pushed the release-please--branches--master branch from b2a41fb to 2e778b6 Compare February 23, 2023 16:30
@dpebot
Copy link
Collaborator

dpebot commented Feb 23, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from 2e778b6 to a253543 Compare February 24, 2023 16:39
@dpebot
Copy link
Collaborator

dpebot commented Feb 24, 2023

/gcbrun

@mirobertod
Copy link

Hi guys, any ETA for this release?
Thanks!

@release-please release-please bot force-pushed the release-please--branches--master branch from a253543 to 729870f Compare March 6, 2023 16:22
@dpebot
Copy link
Collaborator

dpebot commented Mar 6, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from 729870f to bf41eb3 Compare March 7, 2023 01:55
@dpebot
Copy link
Collaborator

dpebot commented Mar 7, 2023

/gcbrun

@furlangiacomo
Copy link

Hello, any update on when this PR will be merged? Thanks!

@release-please release-please bot force-pushed the release-please--branches--master branch from bf41eb3 to 673aa95 Compare March 13, 2023 18:28
@dpebot
Copy link
Collaborator

dpebot commented Mar 13, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from 673aa95 to 55ec581 Compare March 14, 2023 16:05
@dpebot
Copy link
Collaborator

dpebot commented Mar 14, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from 55ec581 to 10dedb8 Compare March 21, 2023 15:55
@dpebot
Copy link
Collaborator

dpebot commented Mar 21, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from 10dedb8 to 5f9c8af Compare March 21, 2023 16:29
@release-please release-please bot removed the release-please:force-run Force release-please to check for changes. label Mar 21, 2023
@release-please release-please bot force-pushed the release-please--branches--master branch from 5f9c8af to 462d960 Compare March 21, 2023 16:42
@dpebot
Copy link
Collaborator

dpebot commented Mar 21, 2023

/gcbrun

@apeabody apeabody added the release-please:force-run Force release-please to check for changes. label Mar 21, 2023
@release-please release-please bot removed the release-please:force-run Force release-please to check for changes. label Mar 21, 2023
@release-please release-please bot force-pushed the release-please--branches--master branch from 462d960 to a13757c Compare March 21, 2023 16:44
@dpebot
Copy link
Collaborator

dpebot commented Mar 21, 2023

/gcbrun

@apeabody apeabody removed their assignment Mar 21, 2023
@apeabody
Copy link
Contributor

We should probably try to include #185 in this breaking release.

@release-please release-please bot force-pushed the release-please--branches--master branch from a13757c to d45c15a Compare March 24, 2023 21:17
@dpebot
Copy link
Collaborator

dpebot commented Mar 24, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from d45c15a to 70fb3d0 Compare March 28, 2023 16:38
@dpebot
Copy link
Collaborator

dpebot commented Mar 28, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from 70fb3d0 to d27c369 Compare March 29, 2023 16:53
@dpebot
Copy link
Collaborator

dpebot commented Mar 29, 2023

/gcbrun

@release-please release-please bot force-pushed the release-please--branches--master branch from d27c369 to a64acd5 Compare April 6, 2023 23:52
@dpebot
Copy link
Collaborator

dpebot commented Apr 6, 2023

/gcbrun

@CharlieC3
Copy link

Would love to see this merged soon, is there something currently blocking it? If #185 is the blocker, I don't see much activity going on there either. For the sake of time, maybe #185 can be included in a later release?

@apeabody
Copy link
Contributor

Would love to see this merged soon, is there something currently blocking it? If #185 is the blocker, I don't see much activity going on there either. For the sake of time, maybe #185 can be included in a later release?

Hi @CharlieC3 - We could push #185 to a later release, however it appears the upgrade guide https://github.com/terraform-google-modules/terraform-google-cloud-storage/blob/master/docs/upgrading_to_v4.0.md may need an addition to cover state migration: #214 (comment)

@imrannayer - Would you happen to be familiar?

@imrannayer
Copy link
Contributor

@apeabody I created bucket using current module version 3.4.1 and then ran terraform apply using code for module version 4.0. I am not able to reproduce the problem mentioned in #214 (comment).
We have been using uniform_bucket_level_access in our module since release 1.7

@apeabody
Copy link
Contributor

@apeabody I created bucket using current module version 3.4.1 and then ran terraform apply using code for module version 4.0. I am not able to reproduce the problem mentioned in #214 (comment). We have been using uniform_bucket_level_access in our module since release 1.7

Thanks @imrannayer! Possibly related to prior major version upgrades.

@dpebot
Copy link
Collaborator

dpebot commented Apr 11, 2023

/gcbrun

@apeabody apeabody merged commit cdc8c67 into master Apr 11, 2023
@apeabody apeabody deleted the release-please--branches--master branch April 11, 2023 23:17
@release-please
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants