Skip to content

Change to JSON key file breaks using relative paths #95

Closed
#100
Closed
Change to JSON key file breaks using relative paths#95
#100
Assignees
rakyll
Labels
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone
Core Stable

Description

@jasonpolites
jasonpolites
opened on Aug 5, 2014

This recent change to using a single JSON file for the key data makes sense but it now breaks if you specify a path relative to the root of the project. By default require(...) will search node_modules if the path specified is relative.

Recommend using more generalized file system operations (e.g. fs & path) so that applications can remain isolated from their environment

Activity

  1. rakyll
    added this to the milestone on Aug 5, 2014
  2. rakyll
    added
    bug
    on Aug 5, 2014

  3. rakyll commented on Aug 5, 2014

    @rakyll
    rakyll
    on Aug 5, 2014
    Contributor

    I will be fixing it while I'm working on #46.

  4. rakyll
    closed this as completedin #100on Aug 8, 2014
  5. jgeewax
    added
    auth
    on Feb 2, 2015
  6. jgeewax
    modified the milestones: , Core Stable on Feb 2, 2015
  7. yoshi-automation
    added
    🚨This issue needs some love.
    triage meI really want to be triaged.
    on Apr 7, 2020
  8. JustinBeckwith
    assigned
    rakyll
    on Feb 1, 2021
  9. chingor13
    added 2 commits that reference this issue on Aug 22, 2022

    Release v0.2.0 (#95)

    689ccb5

    fix: better support for fallback mode (#95)

    6b37ca9
  10. chingor13
    added a commit that references this issue on Sep 12, 2022

    chore: fix the wrong post processor image (#95)

    6d77967

  11. 72 remaining items

  12. codyoss
    added a commit that references this issue on Mar 5, 2026

    chore(deps): update dependency hard-rejection to v2 (#95)

    5796ea2
  13. GautamSharda
    added a commit that references this issue on Mar 5, 2026

    v1.2.0 (#95)

    a1625d9
  14. sofisl
    added 2 commits that reference this issue on Mar 5, 2026

    chore: merge pull request #95 from googleapis/gcp-metadata-migration

    7c8851d

    fix: correctly set compress/gzip option when false (#95)

    081b383
  15. codyoss
    added 3 commits that reference this issue on Mar 9, 2026

    chore(deps): update dependency mocha to v6

    8c8db36

    chore(deps): update dependency mocha to v6

    2315efc

    chore: update github actions configuration (#95)

    92ca798
  16. GautamSharda
    added 3 commits that reference this issue on Mar 12, 2026

    build: Add docuploader credentials to node publish jobs (#95)

    c2cfe5d

    build: Add docuploader credentials to node publish jobs (#95)

    1f5e34a

    chore: convert operation.ts to es6 (#95)

    3151679
  17. thiyaguk09
    added a commit that references this issue on Mar 18, 2026

    Get the full Topic name. (googleapis#95)

    8ebaaea
  18. GautamSharda
    added 2 commits that reference this issue on Mar 23, 2026

    Check if Error is FamilyError for autoCreate. (#95)

    87dc9d6

    Check if Error is FamilyError for autoCreate. (#95)

    0a1930f
  19. shivanee-p
    added a commit that references this issue on Mar 27, 2026

    Check if Error is FamilyError for autoCreate. (#95)

    cf581d3
  20. thiyaguk09
    added a commit that references this issue on May 5, 2026

    Check if Error is FamilyError for autoCreate. (googleapis#95)

    cd6c8e8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions