We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In order to pass a context to a microservice environement variable becomes very handy
There is way to pass directly an environement variable to a microservice through configuration. Only using : ENV=test npm test
ENV=test npm test
N/A
We should be able to pass en environment variable through the restqa config file
have the following in the .restqa.yml file
.restqa.yml
version: 0.0.1 metadata: code: -NEXT-BEST-OFFER-API name: "@next-best-offer/api" description: Delicious Microservice maintained with RestQA tests: local: port: "3000" command: npm start envs: FOO: bar performance: tool: artillery
Yes
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
👀 Background
In order to pass a context to a microservice environement variable becomes very handy
✌️ What is the actual behavior?
There is way to pass directly an environement variable to a microservice through configuration.
Only using :
ENV=test npm test
🕵️♀️ How to reproduce the current behavior?
N/A
🤞 What is the expected behavior?
We should be able to pass en environment variable through the restqa config file
😎 Proposed solution.
have the following in the
.restqa.yml
file🙏 Would you be willing to submit a PR?
Yes
Code of Conduct
The text was updated successfully, but these errors were encountered: