{{ message }}
Repository navigation
Conversation
CKAN may validate the schema when the resource is created: ckanext-neso rejects an upsert resource without schema.primaryKey. The schema was only added by the post-write resource_patch, so datastore_create with a new upsert resource always failed with 'CKAN denied resource_create'.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
datastore_createwith a newresourcedict andingestion_mode: upsertalways fails withCKAN denied resource_create.The service creates the CKAN resource without a schema and only adds it afterwards via
resource_patch. ckanext-neso validates upsert resources at create time and rejects them whenschema.primaryKeyis missing, so the create never gets that far.Fix
Include the schema the service already built in the
resource_createcall. The post-write sync is unchanged; it patches the same schema, so aircan's upsert type-change guard doesn't fire.Reproduced on dev (api.dev.neso.energy) during UAT. A resource created with the same typed schema passes both CKAN checks there, and the upsert flow works end to end.