-
Notifications
You must be signed in to change notification settings - Fork 125
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
Add aws_sagemaker_mlflow_tracking_server resource #1564
base: main
Are you sure you want to change the base?
Conversation
e7ece3b
to
08496b3
Compare
/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml" |
/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml" |
2 similar comments
/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml" |
/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml" |
@turkenf do you mind running the tests again? The error may have been transient, doesn't look code related |
/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml" |
@Ezzmo It looks like the provider pod logs have some info on errors |
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.
Signed-off-by: Ezzmo <[email protected]>
fdaee1c
to
5ff8a59
Compare
Signed-off-by: Ezzmo <[email protected]>
Signed-off-by: Ezzmo <[email protected]>
Signed-off-by: Ezzmo <[email protected]>
5ff8a59
to
835d924
Compare
Thanks @turkenf , I missed those (oops) I've updated the references for the related role and policy, fixed the S3 reference and some metadata mistakes |
/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml" |
@turkenf Looks like it needs another run |
@@ -2281,6 +2281,8 @@ var TerraformPluginSDKExternalNameConfigs = map[string]config.ExternalName{ | |||
"aws_sagemaker_image": config.ParameterAsIdentifier("image_name"), | |||
// SageMaker Code Images can be imported using the name | |||
"aws_sagemaker_image_version": config.IdentifierFromProvider, | |||
// Sagemaker MLFlow tracking server can be imported using the name | |||
"aws_sagemaker_mlflow_tracking_server": config.NameAsIdentifier, |
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.
To use NameAsIdentifier
as an external name, the resource must be imported with the name, and the name argument must be present. See https://github.com/crossplane/upjet/blob/main/docs/adding-new-resource.md#case-1-name-as-identifier
When I look at the resource's import document, it says that it can be imported with workteam_name
. I assume there is a mistake here and that is because I don't see an argument called workteam_name
. Instead, tracking_server_name
can be used, and in this case, the most appropriate external name configuration is ParameterAsIdentifier.
Could you please regenerate the resource with the following configuration?
"aws_sagemaker_mlflow_tracking_server": config.NameAsIdentifier, | |
"aws_sagemaker_mlflow_tracking_server": config.ParameterAsIdentifier("tracking_server_name"), |
Description of your changes
This PR adds the
mlflowtrackingservers.sagemaker.aws.upbound.io
resourceI have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested