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

Allow "Connect" for any and all nodes #401

Merged
merged 1 commit into from
Jul 10, 2020

Conversation

adawalli
Copy link
Contributor

@adawalli adawalli commented Jul 8, 2020

The 'consul_connect_enabled' is now the root of truth for allowing
Consul connect functionality. This remediates the current functionality
where Connect is only allowed on Consul SERVER nodes.

Addresses #400

The 'consul_connect_enabled' is now the root of truth for allowing
Consul connect functionality. This remediates the current functionality
where Connect is only allowed on Consul SERVER nodes.

Addresses ansible-collections#400
@adawalli
Copy link
Contributor Author

adawalli commented Jul 8, 2020

You can now use the consul_connect_enabled to enable/disable connect on a per server basis (e.g., inventory, variables, defaults)...However your team requires connect.

@adawalli
Copy link
Contributor Author

adawalli commented Jul 8, 2020

@perlboy - I see that one of the check failed, but it's only because resources couldn't be created in a timely matter - is there a way I can rerun the tests

@adawalli
Copy link
Contributor Author

@lanefu - do you know how I can rerun the molecule test case?

@lanefu
Copy link
Contributor

lanefu commented Jul 10, 2020

@adawalli I re-ran the tests.. not sure if you're able to re-run... you'd see a re-run button from the detailed test view if so

@lanefu lanefu merged commit 1e286f8 into ansible-collections:master Jul 10, 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.

None yet

2 participants