Skip to content
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.

Support cluster replication #98

Open
iwarapter opened this issue May 24, 2021 · 0 comments
Open

Support cluster replication #98

iwarapter opened this issue May 24, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@iwarapter
Copy link
Owner

iwarapter commented May 24, 2021

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

When deploying configuration in a cluster pingfederate, replication after a successful apply is required.

This should support the following use cases:

  • Replication is performed after all resources requiring change have completed successfully.
  • Any failed apply results in no replication.
  • This should all be achieved within a single apply i.e dont apply then need to plan & apply afterwards to detect the requirement to replicate.

References

@iwarapter iwarapter added the enhancement New feature or request label May 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant