Skip to content
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

resource apstra_telemetry_service_registry_entry - not all storage_schema_path values allowed? #723

Open
chrismarget-j opened this issue Jul 15, 2024 · 1 comment
Assignees

Comments

@chrismarget-j
Copy link
Collaborator

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?

@rajagopalans rajagopalans self-assigned this Jul 16, 2024
@chrismarget-j
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants