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.

Sign up for GitHub

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

Jump to bottom

Support for Vertex AI resources #9298

Closed
charles-bluett opened this issue Jun 4, 2021 · 6 comments
Closed

Support for Vertex AI resources #9298

charles-bluett opened this issue Jun 4, 2021 · 6 comments
Labels
enhancement new-resource size/xl
Milestone
Goals

Comments

@charles-bluett
Copy link

charles-bluett commented Jun 4, 2021 •
edited by melinath
Loading

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Currently none of the recently released Vertex AI resources are supported by the terraform provider.

https://cloud.google.com/vertex-ai/docs/reference

New or Affected Resource(s)

  • google_vertex_ai_*

Batch Predictions
CustomJobs
dataLabeling
datasets
endpoints
Feature stores (v1beta1)
hyperparameter Tuning Jobs
indexEndpoints (v1beta1)
indexs (v1beta1)
metadata stores (v1beta1)
Model deployment monitoring Jobs (v1beta1)
Models
operations
pipeline Jobs
Specialist Pools
studies (v1beta1)
tensorboards (v1beta1)
Training Pipelines

References

https://cloud.google.com/vertex-ai/docs/reference
There is an existing request for Feature Stores #9264

  • #0000
@rileykarson rileykarson added this to the Goals milestone Jun 7, 2021
@upodroid upodroid mentioned this issue Jun 11, 2021
Merged
5 tasks
This was referenced Jun 21, 2021
Merged
Merged
Merged
Merged
@upodroid upodroid mentioned this issue Jun 22, 2021
Merged
5 tasks
@jamiet-msm
Copy link

Would really really like to see Feature Store supported please folks!

@upodroid
Copy link
Contributor

upodroid commented Jul 5, 2021

It is being worked on.

@upodroid upodroid mentioned this issue Jul 5, 2021
Merged
5 tasks
This was referenced Jul 9, 2021
Merged
Merged
@marktru
Copy link

marktru commented Sep 10, 2021

This needs to have the milestone unassigned and a P1 priority. Relates to issue http://b/199214105.

@simonbutt-datatonic simonbutt-datatonic mentioned this issue Nov 19, 2021
Closed
5 tasks
This was referenced Nov 30, 2021
Merged
Merged
@trodge trodge mentioned this issue Jun 23, 2022
Closed
5 tasks
@trodge trodge mentioned this issue Aug 1, 2022
Closed
5 tasks
This was referenced Sep 18, 2022
Merged
Merged
@trodge trodge mentioned this issue Sep 20, 2022
Merged
5 tasks
This was referenced Sep 29, 2022
Merged
Merged
Merged
This was referenced Oct 26, 2022
Merged
Merged
@shotarok shotarok mentioned this issue Nov 7, 2022
Merged
5 tasks
This was referenced Nov 8, 2022
Merged
Merged
Merged
Merged
@shotarok shotarok mentioned this issue Nov 25, 2022
Merged
5 tasks
@shotarok
Copy link
Contributor

GoogleCloudPlatform/magic-modules#6759 added google_vertex_ai_tensorboard.

This was referenced Nov 28, 2022
Merged
Merged
Merged
Merged
Merged
Merged
@shotarok shotarok mentioned this issue Dec 11, 2022
Merged
5 tasks
@ghost ghost mentioned this issue May 17, 2023
Closed
This was referenced May 17, 2023
Merged
Merged
This was referenced Jun 7, 2023
Merged
Merged
Merged
Merged
@melinath
Copy link
Collaborator

Since about half of the requested resources have been implemented, we're closing this issue; it's not possible to tell how many of the thumbs are due to resources that have already been implemented. For anyone following this issue: Please open new (individual) issues for any resources that you want to see in the providers that are not yet supported. Thank you!

modular-magician added a commit to modular-magician/terraform-provider-google that referenced this issue Oct 20, 2023
@modular-magician
Vgm vpc subseg (hashicorp#9298)
2797fb0 
* First commit for VPC sub-segmentation feature. All relevant resources and tests updated.

* Adding access levels instead of using a fake access level name. Also moving a VPC network to the top level instead of (incorrectly) inside another resource.

* Fixing conflict between ip_subnetworks and vpc_ip_subnetworks

* Undoing changes to access level condition test

* Undoing changes to access level condition test

* Ran gofmt

* Re-adding access level conditions tests

* Changing resource names to camel case to match what the HTTP response from the API returns. Also removing the 'resource' field because it's behind an allowlist.

* Parameterizing the names of VPC networks created in tests

* Fixing access level condition test

* Fixed formatting with gofmt

* Added missing fields in egress_from for service perimeter test.

* Added "required: true" for AccessLevel.VpcNetworkSource.network field to
match description.

* Added egress source changes to test data in: example_access_context_manager_service_perimeter.tfplan.json

* Add Egress Source/source restriction changes to example_access_context_manager_service_perimeter.tf

* Attempt to fix example_access_context_manager_service_perimeter.tfplan.json to make it parse correctly

* Add Egress Source to expected tcg test result data

* Fixing expected output format in example_access_context_manager_service_perimeter.json

* Fix Access Level format in expected output in example_access_context_manager_service_perimeter.json

---------

Co-authored-by: vgm <[email protected]>
Co-authored-by: Viktor Moros <[email protected]>
[upstream:d30384c9aa2002c56102ce4c8f0c76c77706b923]

Signed-off-by: Modular Magician <[email protected]>
modular-magician added a commit that referenced this issue Oct 20, 2023
@modular-magician
Vgm vpc subseg (#9298) (#16327)
13a4de0 
* First commit for VPC sub-segmentation feature. All relevant resources and tests updated.

* Adding access levels instead of using a fake access level name. Also moving a VPC network to the top level instead of (incorrectly) inside another resource.

* Fixing conflict between ip_subnetworks and vpc_ip_subnetworks

* Undoing changes to access level condition test

* Undoing changes to access level condition test

* Ran gofmt

* Re-adding access level conditions tests

* Changing resource names to camel case to match what the HTTP response from the API returns. Also removing the 'resource' field because it's behind an allowlist.

* Parameterizing the names of VPC networks created in tests

* Fixing access level condition test

* Fixed formatting with gofmt

* Added missing fields in egress_from for service perimeter test.

* Added "required: true" for AccessLevel.VpcNetworkSource.network field to
match description.

* Added egress source changes to test data in: example_access_context_manager_service_perimeter.tfplan.json

* Add Egress Source/source restriction changes to example_access_context_manager_service_perimeter.tf

* Attempt to fix example_access_context_manager_service_perimeter.tfplan.json to make it parse correctly

* Add Egress Source to expected tcg test result data

* Fixing expected output format in example_access_context_manager_service_perimeter.json

* Fix Access Level format in expected output in example_access_context_manager_service_perimeter.json

---------



[upstream:d30384c9aa2002c56102ce4c8f0c76c77706b923]

Signed-off-by: Modular Magician <[email protected]>
@github-actions GitHub Actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, 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 Nov 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement new-resource size/xl
Projects
None yet
Milestone
Goals
Development

No branches or pull requests
8 participants
@melinath @shotarok @rileykarson @upodroid @edwardmedia @charles-bluett @jamiet-msm @marktru