OCI schema in the registry is missing Java

[gioandtonic]

File: themes/default/content//registry/packages/oci/schema.json just have csharp, go, nodejs and python. It should have Java too.

[jkodroff]

@claude How is this possible given that we have Java examples, which pull from the schema? It looks like the schema might not be getting published alongside the provider itself.

[claude]

Claude finished @jkodroff's task in 2m 10s —— View job

---

Why oci/schema.json is missing java

• Examine how schema.json is generated/published for packages
• Check the oci package YAML and how schema is fetched
• Determine why Java is missing from the published schema
• Report findings

---

Short version: your hypothesis is right. The registry does not add or strip the language block — it copies the provider's published schema verbatim. The Java SDK config simply isn't in the schema that pulumi-oci publishes, so it's absent from the copy we serve. The Java examples you see are generated independently by our docs pipeline, which is why they exist even without a java language block.

How the served schema.json is produced

In tools/resourcedocsgen/cmd/docs/registry.go, genResourceDocsForPackageFromRegistryMetadata:

1. Fetches the schema, preferring the Pulumi Registry service (getSchemaFromRegistry, registry.go:158) and falling back to raw VCS (getSchemaFromVCS, registry.go:225).
2. Writes those bytes verbatim to schema.json via writeSchemaFile (registry.go:52) — os.WriteFile(..., schemaBytes, ...). No transformation of the language map happens anywhere in this path.

For oci the source is pinned in themes/default/data/registry/packages/oci.yaml:14:

schema_file_url: https://raw.githubusercontent.com/pulumi/pulumi-oci/v4.14.0/provider/cmd/pulumi-resource-oci/schema.json

So csharp, go, nodejs, python and no java is exactly what pulumi-oci's own provider/cmd/pulumi-resource-oci/schema.json contains at v4.14.0. For bridged providers, the language.java block is only present if the bridge main.go is configured to emit Java SDK config; for many bridged providers (oci included) the Java SDK is produced by a separate pulumi-java-gen pass and the java key is never written into the committed/published schema.

Why Java examples still appear

The Java code samples on the page are not read from a language.java block. They're generated by our docs generator (generateDocsFromSchema), which converts each resource's example program to every target language using the pulumi-java codegen we vendor (tools/resourcedocsgen/go.sum:339, pulumi-java v1.26.1) — see the lJava / CreationExampleSyntax[lJava] handling in pkg/docs/templates/resource.tmpl. Example conversion to Java doesn't require the schema to declare a java language block, so "we have Java examples" and "the schema has no java key" are fully consistent.

Where to fix it

This isn't a registry bug — we faithfully serve what the provider publishes. To get java into the served schema.json, the fix belongs upstream in pulumi/pulumi-oci: configure the bridge to include the Java SDK in the schema's language map (so the java block lands in provider/cmd/pulumi-resource-oci/schema.json and in what's published to the registry service). Once a release with that change is picked up here, the served schema will include it automatically.

Note: I couldn't fetch the live schemas to confirm which fetch path (registry service vs. VCS) v4.14.0 resolved through — outbound network is blocked in this run — but it doesn't change the conclusion, since both paths write the bytes unmodified.
• branch claude/issue-10280-20260604-1543

[jkodroff]

@gioandtonic Could you provide some additional information on the impact of Java not being in schema.json? It does not affect the behavior of the provider or its SDKs as far as I know.