Skip to content

functions/composer-storage-trigger/index.js sends nonexistent argument "iap.jwt" to "makeIapPostRequest" #1602

Closed

Description

@starmandeluxe

It looks like the final argument in makeIapPostRequest ("jwt") was removed at some point (43cb78c#diff-03c121b657e9255e31ace2345598d678R152), but for some reason the code sample still provides it in the call to this function:

Why?

Activity

  1. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    and removed
    triage meI really want to be triaged.
    on Feb 11, 2020
  2. fhinkel commented on Feb 11, 2020

    @fhinkel
    Contributor

    @ace-n , could you have a look at this functions sample? Thanks

  3. ace-n commented on Feb 12, 2020

    @ace-n
    Contributor

    @leahecole owns this sample (per CODEOWNERS) - over to you 🙂

  4. added
    api: storageIssues related to the Cloud Storage API.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    and removed
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on Mar 24, 2020
  5. added
    api: composerIssues related to the Managed Service for Apache Airflow API.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    and removed
    🚨This issue needs some love.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    on Apr 22, 2020
  6. meredithslota commented on Apr 22, 2020

    @meredithslota
    Contributor

    I'm not sure if this makes sense but I'm adding the "composer" label so this is surfaced to our team, and dropping priority to P2.

  7. leahecole commented on Jun 29, 2020

    @leahecole
    Contributor

    I'm investigating this now. I tried running the code in the relevant tutorial as is, and it seems to work - the DAG triggers and prints the appropriate info.

    I retried adding in the jwt parameter like it was before, and the DAG triggered then too, printing the appropriate info. This occurred because the makeIapPostRequest function never reads this value. The fact that the function never reads the value is likely why it was removed in this PR that was running eslint - it removed unused parameters. The line that you highlighted managed to get leftover somehow, but has since been updated. There are now no longer any references to this unused jwt - the ones that remain are used in the service account signature request.

    Thank you for opening this - I'm going to close it because as far as I can tell, the code doesn't need any updates at this time.

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

Metadata

Metadata

Assignees

Labels

api: composerIssues related to the Managed Service for Apache Airflow API.priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions