-
Notifications
You must be signed in to change notification settings - Fork 76
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
feat(networkconnectivity): add Service Connection Policy support #624
feat(networkconnectivity): add Service Connection Policy support #624
Conversation
Working on a fix for this in |
Depends on fix included in #631 |
It might be better to test the Upjet update in this PR. |
Sure I'll rebase this onto that. brb |
0bd131b
to
ac1905f
Compare
Rebased onto #631 |
/test-examples="examples/networkconnectivity/v1beta1/serviceconnectionpolicy.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your effort @rickard-von-essen, left two comments for you to consider.
examples/networkconnectivity/v1beta1/serviceconnectionpolicy.yaml
Outdated
Show resolved
Hide resolved
/test-examples="examples/networkconnectivity/v1beta1/serviceconnectionpolicy.yaml" |
1 similar comment
/test-examples="examples/networkconnectivity/v1beta1/serviceconnectionpolicy.yaml" |
Great! Very happy to finally get this to the finishing line. This was a bit rough learning curve for me. 🫠 |
Thank you for your interest and effort @rickard-von-essen. Apart from my question above, in order to move this PR forward, I will need to take over the upjet upgrade PR and make some tests and additions there. I see changes in the APIs files of many resources, I will check them separately in the upjet upgrade PR and make the necessary additions/changes (will add the new ref fields from v1beta2 to v1beta1 apis). After merging the upgrade PR, we can rebase this PR and move it forward. |
Sounds great! Thanks for the support and please ping me there if there are any questions or anything I help out with. |
The upjet upgrade PR is merged @rickard-von-essen. Could you please rebase your branch to the main and squash your commits to make the commit history clean? |
This adds support for google_network_connectivity_service_connection_policy Terraform resource, see https://registry.terraform.io/providers/hashicorp/google/5.39.1/docs/resources/network_connectivity_service_connection_policy Signed-off-by: Rickard von Essen <rickard.von.essen@gmail.com>
Signed-off-by: Rickard von Essen <rickard.von.essen@gmail.com>
Signed-off-by: Rickard von Essen <rickard.von.essen@gmail.com>
Signed-off-by: Rickard von Essen <rickard.von.essen@gmail.com>
Signed-off-by: Rickard von Essen <rickard.von.essen@gmail.com>
b1c12db
to
5ce160a
Compare
/test-examples="examples/networkconnectivity/v1beta1/serviceconnectionpolicy.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many thanks @rickard-von-essen, LGTM 🙌
Description of your changes
This adds support for
google_network_connectivity_service_connection_policy
Terraform resource, see Terraform - Google - Service Connection Policy.Includes #631
I have:
make reviewable
to ensure this PR is ready for review.Addedbackport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
Via uptest: https://github.com/crossplane-contrib/provider-upjet-gcp/actions/runs/11480002642