You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes#4588
This simply a result of executing `make tfgen`. There is no impact on
SDKs its seems. There should be however impact on the registry.
This is a little un-intuitive but schema.json does not get reused for
SDK generation. Instead we have something like this:
```
schemaJson := tfgen("schema")
nodeSDK := tfgen("node")
javaSDK := tfgen("java")
```
It looks like CI is missing a check that re-generating schema.json with
`make tfgen` is a no-change operation, allowing this to drift and break
registry. Filing an issue in ci-mgmt.
pulumi/ci-mgmt#1090
Consider introducing CI checks making sure that the published schema.json for bridged providers is up-to-date.
Specifically:
make tfgen
on CIschema.json
compared to the checked in versionWe need the generated schema.json to be up-to-date to what would be computed from the checked in inputs.
We seem to be missing such a check, causing this issue where registry descriptions for aws.iam.Role got wiped:
pulumi/pulumi-aws#4588
There might be alternative ways of fixing this by re-examining how registry is consuming schema.json from the bridged provider repo.
The text was updated successfully, but these errors were encountered: