gatsby-source-drupal - pull only nodes and menus?

I’ve been through the issue queue and could not find any reference for that.

I have a Drupal installation that has the GrpahQL and JsonAPI module enabled. From what I saw, the gatsby-source-drupal plugin pulls from the JSON API only nodes, file, and menu entities. I have custom entities that appear in the JSON API endpoint but the grpahql explorer of my Gatsby ignores them.

Anything I’m missing? I also looked on the filters in plugin option but that did not do the trick as well.

[RoySegall]

@smthomas Permissions are correct. Since My drupal is only for gatsbyjs and some other microservices I did something like this:

/**
 * Implements hook_entity_access().
 */
function my_module_entity_access(\Drupal\Core\Entity\EntityInterface $entity, $operation, \Drupal\Core\Session\AccountInterface $account) {

  if ($operation != 'view') {
    // Not a view operation, skip this one.
    return;
  }

  if ($entity->getEntityType()->id() == 'user') {
    // Don't expose user via this hook.
    return;
  }

  // All entities, beside user, are allowed to be watched.
  return \Drupal\Core\Access\AccessResult::allowed();
}

[smthomas]

I spent some time testing this locally and I was able to get other entities to show up correctly. A few things that need to be checked:

• The cache sometimes needs to be cleared. At first my new entities did not show up until I ran a gatsby clean and cleared the Drupal cache
• Permissions are important. I was not use a user/password in my gatsby-config.js and this made some entities not show up. For me, I was logged in locally so I could see all the entities at the /jsonapi endpoint. However, if I opened an incognito/private browsing window and went to the /jsonapi endpoint you might start seeing less data because of permissions. The solution is to make sure you use a user/password in your gatsby-config.js that has adequate permissions

I hope that helps. Let me know if you are still seeing the same issue.