-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
New Resource: aws_sagemaker_training_job #2955
Conversation
aws/tags_sagemaker.go
Outdated
@@ -0,0 +1,119 @@ | |||
package aws |
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.
This file is a copy of the file in #2478
aws/validators.go
Outdated
@@ -664,6 +664,24 @@ func validateS3BucketLifecycleRuleId(v interface{}, k string) (ws []string, erro | |||
return | |||
} | |||
|
|||
func validateSagemakerName(v interface{}, k string) (ws []string, errors []error) { |
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.
This function has been copied from the same file in #2478
2e30876
to
d8969b3
Compare
c23ff51
to
87ead61
Compare
87ead61
to
9dbbfcc
Compare
9dbbfcc
to
69f3089
Compare
The build has failed due to S3 errors in |
The build error is unrelated to this PR |
looks like we have a check failing. Has anyone had time to assess or review criticality of the failure? |
@bcornils I'll merge master and build again, the error was unrelated to this change last time I checked |
🙌 |
353a620
to
8e0399a
Compare
Hi @ddcprg 👋 Thanks so much for submitting this and sorry for the delayed review process. We have recently merged in a bunch of the Sagemaker resources surrounding model deployment and now we are ready to review/work through other parts of Sagemaker. Could you please rebase this PR? The shared files currently conflicting should be stable now for this pull request. 🤞 |
hi @bflad no problem at all, I thought this one was going to be left out for being a static non-deletable resource in AWS. I'll try to take a look at this today and leave an update here |
@bflad I've brought this branch up to date, feel free to take a look any time, cheers |
@ddcprg do you have any idea if this will get merged anytime soon? |
hey @nicholasgcoles I'm not able to tell, I was expecting some feedback from @bflad |
Notification of Recent and Upcoming Changes to ContributionsThank you for this contribution! There have been a few recent development changes that affect this pull request. We apologize for the inconvenience, especially if there have been long review delays up until now. Please note that this is automated message from an unmonitored account. See the FAQ for additional information on the maintainer team and review prioritization. If you are unable to complete these updates, please leave a comment for the community and maintainers so someone can potentially continue the work. The maintainers will encourage other contributors to use the existing contribution as the base for additional changes as appropriate. Otherwise, contributions that do not receive updated code or comments from the original contributor may be closed in the future so the maintainers can focus on active items. For the most up to date information about Terraform AWS Provider development, see the Contributing Guide. Additional technical debt changes can be tracked with the As part of updating a pull request with these changes, the most current unit testing and linting will run. These may report issues that were not previously reported. Action Required: Terraform 0.12 SyntaxReference: #8950 Version 3 and later of the Terraform AWS Provider, which all existing contributions would potentially be added, only supports Terraform 0.12 and later. Certain syntax elements of Terraform 0.11 and earlier show deprecation warnings during runs with Terraform 0.12. Documentation and test configurations, such as those including deprecated string interpolations ( Action Required: Terraform Plugin SDK Version 2Reference: #14551 The Terraform AWS Provider has been upgraded to the latest version of the Terraform Plugin SDK. Generally, most changes to contributions should only involve updating Go import paths in source code files. Please see the referenced issue for additional information. Action Required: Removal of website/aws.erb FileReference: #14712 Any changes to the Upcoming Change of Git Branch NamingReference: #14292 Development environments will need their upstream Git branch updated from Upcoming Change of GitHub OrganizationReference: #14715 This repository will be migrating from https://github.com/terraform-providers/terraform-provider-aws to https://github.com/hashicorp/terraform-provider-aws. No practitioner or developer action is anticipated and most GitHub functionality will automatically redirect to the new location. Go import paths including |
Hey @ddcprg, can you rebase and address V2 changes mentioned above and then ill take a look and review this PR. |
@DrFaust92 I've left the company where this code is and they removed it as collaborator no long ago so I cannot longer make changes to this PR. I'll have to close and open a new one in my own fork - AFAIK there is no way to change the PR to another fork. I'd like to confirm whether this is actually going to be merged as I don't have a lot of spare time at the moment, last feedback I got is this was a static resource and should not be part of terraform - I think this was before the AWS provider was refactored into its own project. |
Let me look at the API and I'll get back to you. I can fork the original branch an continue of you would like. |
any updates on this one @DrFaust92 ? if we can continue where we left that'd be great |
Hey @ddcprg if you are willing to continue with this PR ill help with the review. Edit: after looking at the API and docs im not so sure this fits in terraform (as previously mentioned) if you can provide a use case for this we can discuss how to go about implementing this. |
Closing, If this is still relevant please open a new issue with the relevant information on why this is resource is needed to be supported by the provider. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Helps resolving #2493