Juniper / terraform-provider-apstra

Apstra Terraform Provider
Apache License 2.0
14 stars 2 forks source link

resource `apstra_telemetry_service_registry_entry` - not all `storage_schema_path` values allowed? #723

Open chrismarget-j opened 1 month ago

chrismarget-j commented 1 month ago

I'm not clear on the rules which relate application_schema to storage_schema_path, but I'm having a problem creating one of these resources:

resource "apstra_telemetry_service_registry_entry" "t" {
  service_name       = "foo"
  application_schema = "{}"
  storage_schema_path = "arp"
}

The error is:

╷
│ Error: error creating new TelemetryServiceRegistryEntry
│ 
│   with apstra_telemetry_service_registry_entry.x,
│   on main.tf line 46, in resource "apstra_telemetry_service_registry_entry" "x":
│   46: resource "apstra_telemetry_service_registry_entry" "x" {
│ 
│ {"errors": {"storage_schema_path": "Invalid choice aos.sdk.telemetry.schemas.arp"}} - http response '422 UNPROCESSABLE ENTITY' at
│ 'https://apstra-2bd238e9-290d-4f8d-9f3a-05b501becd14.aws.apstra.com/api/telemetry-service-registry?async=full'
╵

If I change arp to generic, this works okay. Only a handful of the validated storage_schema_path values seem to work. Is it because they're not valid, or because my (empty) application schema can't use that path?

chrismarget-j commented 1 month ago

I think this was resolved by #726 - please confirm @rajagopalans?