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

Env var support #52

Merged
merged 2 commits into from
Mar 6, 2020
Merged

Conversation

bouskaJ
Copy link
Collaborator

@bouskaJ bouskaJ commented Mar 6, 2020

No description provided.

Copy link
Member

@christophd christophd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool idea!

I suggest that we use a common env var name prefix like YAKS_ so all YAKS runtime related env vars share the same prefix. We should also use a common prefix per test step module. So for yaks-testing-camel-k it would be something like YAKS_CAMELK_.

This way we can separate env var settings over various test step modules and make sure not to collide with others.

@bouskaJ
Copy link
Collaborator Author

bouskaJ commented Mar 6, 2020

Agree. I will go with YAKS_CAMELK_MAX_ATTEMPTS and YAKS_CAMELK_DELAY_BETWEEN_ATTEMPTS.

@christophd christophd merged commit 5a35524 into citrusframework:master Mar 6, 2020
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 this pull request may close these issues.

3 participants