Update hubspot source documentation with correct scopes

[lucaswiley]

What

Hubspot source documentation has incorrect scopes for companies, deals, owners and a few others, which leads to nulling out of tables in the destination because it throws a 403 on the Hubspot API. Does not throw an error within Airbyte so it's a bit mysterious.

How

Update the docs to list the correct scopes.

Recommended reading order

1. x.java
2. y.python

🚨 User Impact 🚨

Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.

Pre-merge Checklist

Expand the relevant checklist and delete the others.

New Connector

Community member or Airbyter

• Community member? Grant edit access to maintainers (instructions)
• Secrets in the connector's spec are annotated with airbyte_secret
• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
• Code reviews completed
• Documentation updated
  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
  • docs/integrations/README.md
  • airbyte-integrations/builds.md
• PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• If new credentials are required for use in CI, add them to GSM. Instructions.
• /test connector=connectors/<name> command is passing
• New Connector version released on Dockerhub by running the /publish command described here
• After the connector is published, connector added to connector index as described here
• Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Secrets in the connector's spec are annotated with airbyte_secret
• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
• Code reviews completed
• Documentation updated
  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
• PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• If new credentials are required for use in CI, add them to GSM. Instructions.
• /test connector=connectors/<name> command is passing
• New Connector version released on Dockerhub and connector version bumped by running the /publish command described here

Connector Generator

• Issue acceptance criteria met
• PR name follows PR naming conventions
• If adding a new generator, add it to the list of scaffold modules being tested
• The generator test modules (all connectors with -scaffold in their name) have been updated with the latest scaffold by running ./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates then checking in your changes
• Documentation which references the generator is updated as needed

[YowanR]

@lazebnyi this is a GA connector, so can you take a quick look and approve the PR if this seems like it make sense, please? This is a doc update cc @Amruta-Ranade

[marcosmarxm]

Thanks @lucaswiley

[marcosmarxm]

Waiting for final approval from @lazebnyi

[lazebnyi]

For property_history only crm.objects.contacts.read is reqired - https://legacydocs.hubspot.com/docs/methods/contacts/get_contacts

Let's just leave crm.objects.contacts.read scope

[lazebnyi]

For engagements stream crm.objects.companies.read, crm.objects.contacts.read, crm.objects.deals.read, tickets, e-commerce scopes are reqired - https://legacydocs.hubspot.com/docs/methods/engagements/get-all-engagements

[lazebnyi]

If you get 403 error on the Hubspot API I think you need check API version.

[lucaswiley]

If you get 403 error on the Hubspot API I think you need check API version.

Thanks! Addressed your review. The 403 is incorrect scopes related, I put screenshot of error in PR description. After changing scopes, 403 is gone.

[Amruta-Ranade]

@lazebnyi this is a GA connector, so can you take a quick look and approve the PR if this seems like it make sense, please? This is a doc update cc @Amruta-Ranade

Thanks for the tag! Looks good to me :)

[lazebnyi]

@lucaswiley Yes 403 is incorect scopes, but may be you use scopes what relevant for other version of API. For some endpoint with different API version we should use different scopes.