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 supoport for OSA deployment_environment_variables setting #377

Open
BjoernT opened this issue Oct 1, 2019 · 6 comments
Open

Add supoport for OSA deployment_environment_variables setting #377

BjoernT opened this issue Oct 1, 2019 · 6 comments

Comments

@BjoernT
Copy link
Contributor

BjoernT commented Oct 1, 2019

Please add playbook support for deployment_environment_variables as we use that OSA override where necessary

- hosts: xxxx
  environment: "{{ deployment_environment_variables | default({}) }}"```
@antonym
Copy link
Contributor

antonym commented Oct 23, 2019

Do you need this in the incremental playbooks that run or do they need to be passed into the run-upgrade script when called?

The upstream scripts should call this in OSA, just wondering where specifically we need to loop this in.

@BjoernT
Copy link
Contributor Author

BjoernT commented Oct 29, 2019

The run-upgrade script should just call playbooks which already should honor these. We need these overrides on all playbooks/tasks which do pip and apt installs

@antonym
Copy link
Contributor

antonym commented Oct 29, 2019

https://gitlab.com/rpco-eng/rpc-upgrades/merge_requests/20/diffs

Just need incremental playbooks?

@BjoernT
Copy link
Contributor Author

BjoernT commented Oct 29, 2019

Please merge all code here as no one is looking at gitlab until we physically move the project.
And yes just the incremental playbooks for now. I don't recall the specific task which failed but it should be easily one around pip/apt

@antonym
Copy link
Contributor

antonym commented Oct 29, 2019

Are you good if I mirror the gitlab repo to github and put notations about where to submit issues? There's not really much testing on github at this point...

@BjoernT
Copy link
Contributor Author

BjoernT commented Oct 29, 2019

I would be ok with that if there is a concerted move to gitlab, for all new projects for example. Otherwise we have another audit problem etc.

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

No branches or pull requests

2 participants