-
Notifications
You must be signed in to change notification settings - Fork 54
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 get_peadm_config task #187
Conversation
@reidmv Can you comment on what's the easiest workflow to test this?
but get
as expected. Also, it's still unclear to me how to quickly bootstrap an environment for bolt to find peadm's tasks. I end up creating |
|
@timidri i always do it a bit of a dirty way to hack it together and drop the module in a directory (ensuring its named to only module name and not author-module) and then create a inventory like
Then something like
works although i think a bolt project file is the correct way to do this |
@reidmv thats cleaner although not sure on whats happening with internal compiler address, PROD is large server no compilers no replica, DR is large server 2 compilers no replica.
|
This task can introspect an existing cluster (when run on a primary node) and return information about how the cluster is currently configured. This will aid in running plans that need to modify the cluster, by reducing the amount of information the user must supply. The task returns data about the cluster in both primary/replica form, as well as A/B form, since different forms are useful in different scenarios.
Improve the readability of the task, and the task description.
In the event a group doesn't exist, or a key doesn't return a value. Don't error, just return nil for those values.
When this was refactored, the wrong defaults were given to the compiler load balancer address variables. They should default to the A and B *servers*, not the A and B postgresql hosts.
The The defaults for those settings are... the values of the In your stack, since it was probably provisioned before we always created the B groups, there probably just aren't values for any of that, in any group. |
Realized this could be a generally useful way of understanding all letter assignments, if we returned compilers as well.
Install matrix test action completed successfully with the
|
This task can introspect an existing cluster (when run on a primary node) and return information about how the cluster is currently configured. In the future, this can be used to aid in running plans that need to modify the cluster, by reducing the amount of information the user must supply. For example, the add_compiler plan, or (future) add_postgresql.
The task returns data about the cluster in both primary/replica form, as well as A/B form, since different forms are useful in different scenarios.