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.

Sign up for GitHub

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

Jump to bottom

Add retry & backoff strategy to late initialization config #879

Open
vijtrip2 opened this issue Jul 27, 2021 · 5 comments
Open

Add retry & backoff strategy to late initialization config #879

vijtrip2 opened this issue Jul 27, 2021 · 5 comments
Assignees
@vijtrip2
Labels
kind/enhancement Categorizes issue or PR as related to existing feature enhancements. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@vijtrip2
Copy link
Contributor

As part of feedback on PR #849 , Add retry-backoff strategy for late initialization of server side defaults.
@vijtrip2 vijtrip2 added the kind/enhancement Categorizes issue or PR as related to existing feature enhancements. label Jul 27, 2021
@vijtrip2 vijtrip2 self-assigned this Jul 27, 2021
@vijtrip2 vijtrip2 mentioned this issue Jul 27, 2021
Merged
@ack-bot
Copy link
Collaborator

ack-bot commented Dec 1, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

@ack-bot ack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 1, 2021
@ack-bot
Copy link
Collaborator

ack-bot commented Dec 31, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle rotten

@ack-bot ack-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 31, 2021
@RedbackThomson
Copy link
Contributor

/remove-lifecycle rotten

@ack-bot ack-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 3, 2022
@ack-bot
Copy link
Collaborator

ack-bot commented Apr 3, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale

@ack-bot ack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 3, 2022
@vijtrip2
Copy link
Contributor Author

vijtrip2 commented Apr 4, 2022

/lifecycle frozen

@ack-bot ack-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vijtrip2 vijtrip2

Labels
kind/enhancement Categorizes issue or PR as related to existing feature enhancements. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
No open projects
ACK Core Team
Status: No status
Milestone
No milestone
Development

No branches or pull requests
4 participants
@RedbackThomson @a-hilaly @vijtrip2 @ack-bot