Add aws_sagemaker_mlflow_tracking_server resource

[Ezzmo]

Description of your changes

This PR adds the mlflowtrackingservers.sagemaker.aws.upbound.io resource

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

I tested locally with uptest. The MlFlow tracking server created successfully and tasks succeeded

[Ezzmo]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[Ezzmo]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[turkenf]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[Ezzmo]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[Ezzmo]

@turkenf do you mind running the tests again? The error may have been transient, doesn't look code related

[jeanduplessis]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[jeanduplessis]

@Ezzmo It looks like the provider pod logs have some info on errors

provider-aws-sagemaker logs
provider-aws-iam logs

[turkenf]

Thank you for your contribution @Ezzmo. When we look at the uptest logs, we see that the resources cannot resolve the references. I left comments about this for you to consider.

[Ezzmo]

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

[turkenf]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[Ezzmo]

@turkenf Looks like it needs another run

[turkenf]

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?

Suggested change

	"aws_sagemaker_mlflow_tracking_server": config.NameAsIdentifier,
	"aws_sagemaker_mlflow_tracking_server": config.ParameterAsIdentifier("tracking_server_name"),

[Ezzmo]

I made the mistake of thinking id was acceptable for NameAsIdentifier

Thanks @turkenf. I've updated

[turkenf]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[turkenf]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

[Ezzmo]

@turkenf Thanks for helping in the Slack channel. Tests ran successfully finally after increasing the timeout.

--- PASS: kuttl (2843.65s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/case (2842.41s)

Hopefully will run successfully here

[turkenf]

/test-examples="examples/sagemaker/v1beta1/mlflowtrackingserver.yaml"

https://github.com/crossplane-contrib/provider-upjet-aws/actions/runs/12280429287

[turkenf]

Many thanks for all your efforts @Ezzmo, the PR looks good to me, except for the commit history :) If you have time, it would be great to squash your commits to keep the commit history clean.

[Ezzmo]

@turkenf Rebasing this is proving very hairy, I'm going to produce a new branch with a new PR with a single commit to clean this all up. I suspect the way I updated my feature branch has caused problems now.