feat(instagram): upgrade SDK to 2.0.0, fix helpers import, add pytest unit + integration tests by Shubhank-Jonnada · Pull Request #327 · Autohive-AI/autohive-integrations

Shubhank-Jonnada · 2026-05-13T21:23:58Z

Summary

Fixes a runtime ModuleNotFoundError: No module named 'helpers' that occurred on every action execution. Root cause: the SDK does not add the integration directory to sys.path, so the actions/ subpackage could not resolve helpers. Fixed by adding sys.path.insert(0, os.path.dirname(__file__)) in instagram.py at load time.
Bumps autohive-integrations-sdk to ~=2.0.0 and updates all response.data accesses across instagram.py, helpers.py, and every action file to use the new FetchResponse object returned by context.fetch().
Replaces the old context.py and test_instagram.py test approach with a clean conftest.py, 57 unit tests (test_instagram_unit.py), and a full live integration test suite (test_instagram_integration.py) following the same pattern as the float integration.

Changes

Bug fix

instagram.py now adds its own directory to sys.path so helpers and the actions/ subpackage resolve correctly at runtime regardless of working directory
Integration.load() now uses an explicit config path to avoid CWD-relative resolution issues

SDK 2.0.0 upgrade

requirements.txt bumped to autohive-integrations-sdk~=2.0.0
config.json version bumped to 2.0.0
All response.data accesses updated across helpers.py, actions/account.py, actions/media.py, actions/comments.py, actions/insights.py

Tests

Removed tests/context.py and tests/test_instagram.py (SDK 1.0 style)
Added tests/conftest.py for sys.path setup
Added tests/test_instagram_unit.py with 57 unit tests covering all actions, the connected account handler, helper functions, and error paths
Added tests/test_instagram_integration.py with live tests for all read actions plus a destructive comment lifecycle test (reply, hide, unhide, delete) gated behind @pytest.mark.destructive

Test plan

pytest instagram/tests/test_instagram_unit.py passes 57/57
pytest instagram/tests/test_instagram_integration.py -m integration passes with a valid INSTAGRAM_ACCESS_TOKEN
pytest instagram/tests/test_instagram_integration.py -m "integration and destructive" passes to verify comment lifecycle

… unit + integration tests - Fix ModuleNotFoundError: add sys.path.insert so actions/ subpackage can resolve helpers - Use explicit config path in Integration.load() to avoid CWD-relative resolution - Bump autohive-integrations-sdk to ~=2.0.0; update all response.data accesses - Replace old context.py/test_instagram.py with conftest.py, 57 unit tests, and live integration tests

github-actions · 2026-05-13T21:24:50Z

🔍 Integration Validation Results

Commit: b5f91bbc100834c6e0aaefefc82c4843d11c0f64 · fix(instagram): add total_count to get_comments output_schema
Updated: 2026-05-14T01:00:41Z

Changed directories: instagram

Check	Result
Structure	⚠️ Passed with warnings
Code	✅ Passed
Tests	✅ Passed
README	✅ Passed
Version	✅ Passed

⚠️ Structure Check output

Validating 1 integration(s)...

============================================================
Integration: instagram
============================================================

Warnings (1):
  ⚠️ Integration should use 'Integration.load()' to load the integration

============================================================
SUMMARY
============================================================
Integrations validated: 1
Total errors: 0
Total warnings: 1

⚠️ Validation passed with warnings - please review

✅ Code Check output


[notice] A new release of pip is available: 26.0.1 -> 26.1.1
[notice] To update, run: pip install --upgrade pip
----------------------------------------
Checking: instagram
----------------------------------------

📦 Installing dependencies...

🐍 Checking Python syntax...
   ✅ Syntax OK

📥 Checking imports...
   ✅ Imports OK

📄 Checking JSON files...
   ✅ JSON files OK

🔍 Linting with ruff...
   ✅ Lint OK

🎨 Checking formatting with ruff...
   ✅ Formatting OK

🔒 Scanning for security issues with bandit...
   ✅ Security OK

🛡️ Checking dependencies for vulnerabilities with pip-audit...
   ✅ Dependencies OK

🔗 Checking config-code sync...
   ✅ Config-code sync OK

🔄 Checking fetch patterns...
   ✅ Fetch patterns OK

========================================
✅ CODE CHECK PASSED
========================================

✅ Tests Check output


Integration   Tests  Coverage        Status
-------------------------------------------
instagram     57/57       98%      ✅ Passed
-------------------------------------------
Total         57/57            ✅ All passed

✅ Tests passed: instagram

✅ README Check output

========================================
✅ README CHECK PASSED
========================================

✅ Version Check output

✅ instagram: 1.0.0 → 2.0.0 (major bump)

========================================
✅ VERSION CHECK PASSED
========================================

…type fields, revert __init__.py to simple imports

Shubhank-Jonnada · 2026-05-13T23:19:51Z

All 57 unit tests passing. Live integration tests performed against a real Instagram Business account — 13/15 passed, 2 skipped (comment structure and lifecycle tests skipped due to no comments on test account posts, not a code issue).

Shubhank-Jonnada · 2026-05-13T23:20:51Z

fully working on beta too!

TheRealAgentK

Update after checking this against the repo's multi-module integration pattern.

Verification I ran for the instagram integration:

uv pip install -r instagram/requirements.txt ✅
python ../autohive-integrations-tooling/scripts/validate_integration.py instagram ✅ with one expected advisory warning about explicit Integration.load(<path>)
python ../autohive-integrations-tooling/scripts/check_code.py instagram ✅
pytest instagram/ -v ✅ 57 passed
pytest instagram/tests/test_instagram_integration.py -m integration -q ✅ 15 skipped locally because INSTAGRAM_ACCESS_TOKEN is not set

Correction to my original framing: the import actions side-effect registration pattern is intentional for multi-module integrations and matches existing integrations in this repo. If the Autohive runtime contract is to add the integration directory to sys.path and import the entry point by filename stem (instagram), then the import/registration concern is not a merge blocker.

The inline comment now frames this as a loader-contract hardening concern only: if the runtime ever loads the entry point by file path under a different module name, actions can register on a second module instance. That is worth confirming or optionally guarding with a small regression test, but it is conditional on loader behavior.

Remaining non-blocking follow-up: get_comments now returns total_count, and tests assert it, but get_comments.output_schema in config.json only declares comments and next_cursor. It would be good to add total_count so schema/docs match runtime output.

TheRealAgentK · 2026-05-14T00:07:37Z


-# Import actions to register handlers
-from instagram import actions  # noqa: F401, E402 - registers action handlers
+import actions  # noqa: F401, E402 - registers action handlers


Update after checking the repo's multi-module integration pattern: this side-effect import is intentional and is consistent with existing integrations such as facebook, aws, and humanitix, where the entry module imports actions for registration and action modules import the integration object from the entry module.

So I would not treat this as a definite bug solely because Instagram is multi-module, and this should be fine if the Autohive runtime contract is to add the integration directory to sys.path and import the entry point by its filename stem (instagram).

The only remaining concern is a loader-contract edge case: if the runtime ever loads the configured entry point by file path under a different module name, the action modules' from instagram import instagram can import this file a second time and register handlers on a different Integration instance. I reproduced that local edge case with importlib.util.spec_from_file_location("instagram_entry", "instagram/instagram.py").

Given the established multi-module pattern, I’d frame this as optional hardening rather than a merge blocker: either confirm the runtime always imports by module stem, or add a small guard/regression test for file-path loading. The simple guard would be to alias the running module before importing actions, e.g. sys.modules.setdefault("instagram", sys.modules[__name__]).

Superseded by updated review text: after checking the multi-module integration pattern, the import-registration concern is conditional on loader behavior and not a definite merge blocker.

…ded by file path

Shubhank-Jonnada · 2026-05-14T01:03:56Z

Addressed the two follow-up items from review.

0790c70 adds sys.modules.setdefault before importing actions so the module is always aliased as 'instagram' even if the runtime loads the entry point by file path under a different name.

b5f91bb adds total_count to the get_comments output_schema in config.json so the schema matches what the action actually returns and what the tests assert.

TheRealAgentK

Latest changes address my prior notes:

total_count is now declared in get_comments.output_schema.
The optional file-path loader hardening was added with the sys.modules.setdefault("instagram", sys.modules[__name__]) alias before importing actions.

I re-ran local checks for instagram:

uv pip install -r instagram/requirements.txt ✅
python ../autohive-integrations-tooling/scripts/validate_integration.py instagram ✅ with the known advisory warning for explicit Integration.load(<path>)
python ../autohive-integrations-tooling/scripts/check_code.py instagram ✅
pytest instagram/ -v ✅ 57 passed
pytest instagram/tests/test_instagram_integration.py -m integration -q ✅ 15 skipped locally because INSTAGRAM_ACCESS_TOKEN is not set

I also verified a standard importlib file-path load with the module pre-inserted in sys.modules; the returned integration object has all 8 action handlers registered.

github-code-quality Bot found potential problems May 13, 2026

View reviewed changes

Comment thread instagram/tests/test_instagram_unit.py Fixed

Comment thread instagram/instagram.py Fixed

Comment thread instagram/tests/test_instagram_unit.py Fixed

Shubhank-Jonnada added 2 commits May 14, 2026 09:34

fix(instagram): resolve ruff lint and formatting errors

be9b405

fix(instagram): fix ruff formatting, use inputs[] for required media_…

4d92d3b

…type fields, revert __init__.py to simple imports

github-code-quality Bot found potential problems May 13, 2026

View reviewed changes

Comment thread instagram/instagram.py Fixed

fix(instagram): apply ruff formatting to integration test file

9c8ecd1

Shubhank-Jonnada requested a review from NinosMan May 13, 2026 23:20

TheRealAgentK previously requested changes May 14, 2026

View reviewed changes

fix(instagram): guard against duplicate Integration instance when loa…

0790c70

…ded by file path

github-code-quality Bot found potential problems May 14, 2026

View reviewed changes

Comment thread instagram/instagram.py Dismissed

fix(instagram): add total_count to get_comments output_schema

b5f91bb

Shubhank-Jonnada requested a review from TheRealAgentK May 14, 2026 01:03

TheRealAgentK approved these changes May 14, 2026

View reviewed changes

Shubhank-Jonnada merged commit ff1d164 into master May 14, 2026
3 checks passed

Shubhank-Jonnada deleted the feat/instagram-sdk-2.0 branch May 14, 2026 01:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(instagram): upgrade SDK to 2.0.0, fix helpers import, add pytest unit + integration tests#327

feat(instagram): upgrade SDK to 2.0.0, fix helpers import, add pytest unit + integration tests#327
Shubhank-Jonnada merged 6 commits into
masterfrom
feat/instagram-sdk-2.0

Shubhank-Jonnada commented May 13, 2026

Uh oh!

github-actions Bot commented May 13, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Shubhank-Jonnada commented May 13, 2026

Uh oh!

Shubhank-Jonnada commented May 13, 2026

Uh oh!

TheRealAgentK left a comment •

edited

Loading

Uh oh!

TheRealAgentK May 14, 2026 •

edited

Loading

Uh oh!

Uh oh!

Shubhank-Jonnada commented May 14, 2026

Uh oh!

TheRealAgentK left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Shubhank-Jonnada commented May 13, 2026

Summary

Changes

Test plan

Uh oh!

github-actions Bot commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Integration Validation Results

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Shubhank-Jonnada commented May 13, 2026

Uh oh!

Shubhank-Jonnada commented May 13, 2026

Uh oh!

TheRealAgentK left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

TheRealAgentK May 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Shubhank-Jonnada commented May 14, 2026

Uh oh!

TheRealAgentK left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

github-actions Bot commented May 13, 2026 •

edited

Loading

TheRealAgentK left a comment •

edited

Loading

TheRealAgentK May 14, 2026 •

edited

Loading