Skip to content

Variable visibility across organizations #16581

Open
@karel-rehor

Description

@karel-rehor

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

  1. Onboard to the GUI and then create a second organization
  2. Switch to the first organization
  3. Create some variables
  4. Switch to the second organization
  5. View variables

Expected behavior:
Assumed that since

  • the variable structure includes orgId
  • query variables would refer to buckets specific to the organization
{id: "0518e92b53623000", orgID: "b772d84752daf340", name: "Felix", description: "", selected: null,…}

... that variables would be visible per organization.

Actual behavior:
I'm seeing variables created in one organization visible in another.

Question: Is this by design or is this an issue?

I can see a case for having variables visible across organizations, but this raises possible security and stability issues.

Screencast

VariablesAcrossOrgs01

Environment info:

  • System info: Run uname -srm and copy the output here
Linux 4.15.0-74-generic x86_64
  • InfluxDB version: Run influxd version and copy the output here
    Detected in nightly build
ts=2020-01-17T08:47:35.390174Z lvl=info msg="Welcome to InfluxDB" log_id=0KOfpHsW000 version=nightly commit=3fa552430 build_date=2020-01-17T08:47:35Z
  • Other relevant environment details: Container runtime, disk info, etc
    browser: Chrome 79

Config:
Copy any non-default config values here or attach the full config as a gist or file.

started with end to end testing enabled

--e2e-testing=true

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions