🐛 Source Jira: Fix check command

[tolik0]

What

This PR updates the check command to verify access to any available resources instead of limiting the check to just the Labels endpoint.

How

Implemented an AvailabilityStrategy in the base class to enable skipping streams without required permissions. Removed should_retry methods to avoid duplicating the logic of skip_http_status_codes, which already handles skipping slices in case of errors. This enhancement ensures that the sync will not fail if the API token lacks permission for certain resources.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Dec 12, 2023 11:04pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[darynaishchenko]

do we really need to try read all streams on check? this is certified connector and check command should run fast. we can check only known permissions/scopes, and availability strategy will work while reading and skip stream if it is not available.

[tolik0]

@darynaishchenko The updated check method now passes if at least one stream is readable. Without this inspection, the check will be successful even without access to any resources.