Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flag to specify location of flow.json #67

Closed
10thfloor opened this issue Feb 20, 2021 · 3 comments
Closed

Flag to specify location of flow.json #67

10thfloor opened this issue Feb 20, 2021 · 3 comments
Assignees
Labels
Feedback Improvement Technical work without new features, refactoring, improving tests

Comments

@10thfloor
Copy link
Contributor

10thfloor commented Feb 20, 2021

Currently you have to run commands from the directory where the flow.json file is located.
It would be great if users could point to the location using a flag, in situations where it's not ideal to run the command from the same directory as the file.

eg:

flow deploy --config ../../flow.json
@10thfloor 10thfloor added Feature A new user feature or a new package API Feedback labels Feb 20, 2021
@devbugging
Copy link
Contributor

Do you mean for project deploy? This will be solved with the current migration of the configuration we are working on. For other commands (beside project) you have a flag --config-path.

@devbugging devbugging added Improvement Technical work without new features, refactoring, improving tests and removed Feature A new user feature or a new package API labels Feb 22, 2021
@10thfloor
Copy link
Contributor Author

Do you mean for project deploy? This will be solved with the current migration of the configuration we are working on. For other commands (beside project) you have a flag --config-path.

Great sounds like we can close this when those changes are merged.

@devbugging
Copy link
Contributor

Implemented in #101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feedback Improvement Technical work without new features, refactoring, improving tests
Projects
None yet
Development

No branches or pull requests

3 participants