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

yaml config file for env #5

Closed
knennigtri opened this issue Dec 13, 2022 · 2 comments · Fixed by #18
Closed

yaml config file for env #5

knennigtri opened this issue Dec 13, 2022 · 2 comments · Fixed by #18

Comments

@knennigtri
Copy link
Owner

Rather than asking a user to manually create the env file and globals file, create a simple yaml file that can extract the values and input them into the postman files.... removing the need to understand postman... and opening the door for less dependency on postman

@knennigtri
Copy link
Owner Author

knennigtri commented Dec 13, 2022

env:
  CLIENT_ID: xzy
  CLIENT_SECRET: xzy
  ORG_ID: xyz
  TECHNICAL_ACCOUNT: xyz
  PRIVATE_KEY: xyz

knennigtri added a commit that referenced this issue Jan 18, 2023
@knennigtri
Copy link
Owner Author

Globals moved to #10

@knennigtri knennigtri changed the title yaml config file to env and globals files yaml config file for env Jan 31, 2023
This was referenced Feb 2, 2023
Merged
@knennigtri knennigtri linked a pull request Sep 26, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant