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

Add back ENV support to environment #962

Merged
merged 7 commits into from
Jun 24, 2022
Merged

Conversation

dpskvn
Copy link
Contributor

@dpskvn dpskvn commented Jun 14, 2022

This is basically a re-implementation of #458 which was dropped in version 2, I believe.

As discussed here: #951, this would cover the scenarios where the dynamic inventory requires a token passed as an environment variable and if you have several accounts (which have different tokens), hard-coding it in the unit file is not an option.

I'm open to suggestions/comments. I know the contributing guidelines say there should be an issue opened first, but there is already one which I mentioned in the previous paragraph and there have been no replies to it.

@fiftin fiftin force-pushed the develop branch 2 times, most recently from 0c60a1b to d3dfbf0 Compare June 21, 2022 13:43
@fiftin
Copy link
Collaborator

fiftin commented Jun 21, 2022

Hi @dpskvn,

I sure we should have another place for environment variables. Perhaps additional textarea for it.

@dpskvn
Copy link
Contributor Author

dpskvn commented Jun 24, 2022

@fiftin The environmental variables are a now a separate text area inside the Environment section. The new database model also reflects that.

@fiftin
Copy link
Collaborator

fiftin commented Jun 24, 2022

Thank you @dpskvn , LGFM, but after merge I will make refactoring to support YAML format instead of JSON (I will rename json to extra_vars, env to env_vars).

@fiftin fiftin merged commit a103e2a into semaphoreui:develop Jun 24, 2022
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.

2 participants