PLT-1346: Introduce Basic OCI

[wcrum]

Current behavior is below, where func() resourceRegistryOciEcr schema handles both ECR and Basic repositories, if needed I can have separation between basic and ecr, but this would require changes to the base resource spectrocloud_registry_oci.

resource "spectrocloud_registry_oci" "r1" {
  name       = "test-nik4"
  type       = "basic" # basic
  endpoint   = "harbor.registry"
  provider_type = "helm"
  credentials {
    credential_type = "basic"
    username = "username"
    password = "password"
  }
}

Additionally, given that OCI registries exist at a tenant level, would need provider.go to support tenant level actions, like the commented client.WithScopeTenant()(c)

terraform-provider-spectrocloud/spectrocloud/provider.go

Lines 240 to 242 in d113161

	//else {
	// client.WithScopeTenant()(c)
	//}

[SivaanandM]

Current behavior is below, where func() resourceRegistryOciEcr schema handles both ECR and Basic repositories, if needed I can have separation between basic and ecr, but this would require changes to the base resource spectrocloud_registry_oci.

resource "spectrocloud_registry_oci" "r1" {
  name       = "test-nik4"
  type       = "basic" # basic
  endpoint   = "harbor.registry"
  provider_type = "helm"
  credentials {
    credential_type = "basic"
    username = "username"
    password = "password"
  }
}

Additionally, given that OCI registries exist at a tenant level, would need provider.go to support tenant level actions, like the commented client.WithScopeTenant()(c)

terraform-provider-spectrocloud/spectrocloud/provider.go

Lines 240 to 242 in d113161

	//else {
	// client.WithScopeTenant()(c)
	//}

So basically registries can be created only and tenant level. and used across the projects. this is handled in resource level itself. not required to update provider.go

[SivaanandM]

Kindly address the review comments. We will prioritize the changes for testing and include them in the corresponding release.