Daniel Mangum

> I'm not sure about the naming though. There could be several v1beta* in GCP as well as v2beta* etc. So, having v1beta1.gcp.crossplane.io and v1.gcp.crossplane.io provider groups seems more accurate...

@muvaf we cannot guarantee that, but the point of having the two different providers is not to map to a specific API for each but rather to have one where...

This proposal is now in motion in https://github.com/crossplane/provider-gcp-beta. I think this is a great forcing function to introduce provider-specific release notes. According to governance, this is enforced on a per-provider...

@jbw976 that is correct. It is hard to say how common it is. It is set on the `BucketClass` for the Gitlab example, but I am not entirely sure it...

@muvaf @negz did this end up getting fixed with the `v1beta1` updates?

@vadasambar sorry for just getting to this! You will need to install `crossplane` before installing `stack-gcp` (recommend the instructions [here](https://crossplane.io/docs/v0.5/install-crossplane.html)). If you want to develop locally and you have your...

@vadasambar Yes! If the stack is installed via a stack package then the CRDs will be installed for you, but if running the controller manager directly locally then you must...

@mcavoyk thanks for opening this! We have considered supporting both structured and unstructured simultaneously (with one taking precedence over the other) by having a field such as `rawStatement` if folks...

@muvaf just wanted to give you a heads up that I am going to open a PR for pinning master to crossplane `v0.6.0` so that we can cherry-pick backport to...

@displague let me know if I can provide any assistance as you get those set up :+1: