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

🚀 [FEATURE]: Inject environment variable to microservice #351

Closed
1 task done
olivierodo opened this issue Mar 12, 2023 · 0 comments · Fixed by #360
Closed
1 task done

🚀 [FEATURE]: Inject environment variable to microservice #351

olivierodo opened this issue Mar 12, 2023 · 0 comments · Fixed by #360
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@olivierodo
Copy link
Member

👀 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

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

🙏 Would you be willing to submit a PR?

Yes

Code of Conduct

  • I agree to follow this project's Code of Conduct
@olivierodo olivierodo added enhancement New feature or request help wanted Extra attention is needed labels Mar 21, 2023
@olivierodo olivierodo added this to the v1.0.0 milestone Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant