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 networking and VPC resources to v1beta1 #145

Closed
infinitecompute opened this issue Mar 2, 2020 · 2 comments · Fixed by #569
Closed

AWS networking and VPC resources to v1beta1 #145

infinitecompute opened this issue Mar 2, 2020 · 2 comments · Fixed by #569
Assignees
Labels

Comments

@infinitecompute
Copy link

infinitecompute commented Mar 2, 2020

What problem are you facing?

Would like a v1beta1 version of networking and VPC resources

How could Crossplane help solve your problem?

Move networking and VPC resources to v1beta1 standards

References

@prasek
Copy link
Contributor

prasek commented Aug 6, 2020

finished via #182

@prasek prasek closed this as completed Aug 6, 2020
@prasek
Copy link
Contributor

prasek commented Aug 6, 2020

@hasheddan just realized that RouteTable is still at v1alpha4, so keeping this open for now.

@prasek prasek reopened this Aug 6, 2020
@muvaf muvaf assigned muvaf and unassigned sahil-lakhwani Feb 24, 2021
@muvaf muvaf added this to Accepted in v1.1 Feb 24, 2021
@muvaf muvaf moved this from Accepted to In Progress in v1.1 Mar 1, 2021
@muvaf muvaf moved this from In Progress to PR Open in v1.1 Mar 2, 2021
@muvaf muvaf closed this as completed in #569 Mar 2, 2021
v1.1 automation moved this from PR Open to Done Mar 2, 2021
@prasek prasek removed this from the v0.8 milestone Mar 2, 2021
@negz negz removed this from Done in v1.1 May 26, 2022
tektondeploy pushed a commit to gtn3010/provider-aws that referenced this issue Mar 12, 2024
…endency

Consume upjet commit 6de200a3a8b0ac77c5f9d122f93db26aacd61960
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants