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

No way to create and affect an Instance Group to an Organization in on go #858

Closed
nodje opened this issue Jul 9, 2024 · 0 comments · Fixed by #859
Closed

No way to create and affect an Instance Group to an Organization in on go #858

nodje opened this issue Jul 9, 2024 · 0 comments · Fixed by #859
Labels
bug Something isn't working new New issue, this should be removed once reviewed

Comments

@nodje
Copy link

nodje commented Jul 9, 2024

Using latest published 2.7.1

As far as I can see, there's no way to bootstrap an AAP2 instance with an ad-hoc Container group affected to an Organization.

The reason is the dependency cycle: Organization -> Instance Group -> Credential -> Organization.

There's this existing mecanism in the Organization Controller, which deactivate the ee and cred affectation when using the vars assign_galaxy_credentials_to_org and assign_default_ee_to_org, which solves a similar issue.

Would it be possible to have similar var for Instance Groups?

@nodje nodje added bug Something isn't working new New issue, this should be removed once reviewed labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working new New issue, this should be removed once reviewed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant