Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Meltano
Meltano
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 465
    • Issues 465
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 24
    • Merge requests 24
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • meltano
  • MeltanoMeltano
  • Issues
  • #2279

Closed
Open
Created Aug 19, 2020 by Douwe Maan@DouweMOwner

Populate primary env var and aliases when invoking plugin or expanding env vars

As suggested in #2208 (comment 388529270):

Perhaps the best option would be to have Meltano write to both the env and env_aliases keys, so that we cover all bases for backward compatibility, but can still recommend the simple <NAMESPACE>_<NAME> vars, and prefer those when writing to .env.

Assignee
Assign to
Fri: Sep 11, 2020
Milestone
Fri: Sep 11, 2020 (Past due)
Assign milestone
Time tracking