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

Configuration as code could use downstream EE as basis - Bug report for Ansible Workshops #1975

Open
ericzolf opened this issue May 22, 2023 · 2 comments
Assignees

Comments

@ericzolf
Copy link
Contributor

Problem Summary

As the lab contains the PAH, which itself has the downstream EEs available, so they could relatively be used as basis EE instead of the upstream one. This would also remove one dependency from the outside world.

Issue Type

Feature Request

Extra vars file

n/a

Ansible Playbook Output

n/a

Ansible Version

n/a

Ansible Configuration

n/a

Ansible Execution Node

Ansible Controller (previously known as Ansible Tower)

Operating System

n/a

@IPvSean
Copy link
Contributor

IPvSean commented Jul 5, 2023

cc @sean-m-sullivan

@sean-m-sullivan
Copy link
Contributor

sean-m-sullivan commented Jul 5, 2023

Will look into this, I think the problem was getting it down with downstream without providing the customer account information, but it was also done before we knew where it was hosted.
Also am looking to update this to latest ee_utilities that uses v3 builder as well.

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

3 participants