-
Notifications
You must be signed in to change notification settings - Fork 241
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
Improvements to PaaSTA Playground #3727
Conversation
cuza
commented
Oct 23, 2023
•
edited
Loading
edited
- added paasta-cronjobs make target
- setup-kubernetes-job
- cleanup-kubernetes-job
- paasta-secrets-sync
- generate_deployments_for_service
- added VSCode debugpy as dev requirement
- made paasta playground not overrwrite existing paasta confs or yelpsoa-configs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i left some comments, but not are really blockers (although, i do feel a little uneasy about setting up an infinite loop that runs every 5s on code folks might be actively iterating on)
.PHONY: paasta-crons | ||
make paasta-cronjobs: | ||
@echo "$$ANNOUNCE_CRONS_BODY" | ||
while true; do make paasta-secrets-sync && make cleanup-kubernetes-jobs; sleep 5; done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm, should we be a little nicer to our devboxes and run these every minute?
and just to verify that my eyes are reading this correctly: we're running this in the foreground so upon ^C we'll stop this loop?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is running every 5s but also is kinda lightweight since is running just using the PaaSTA playground stuff, unless you made your playground super heavy with lots of test svcs it should be fine. I also tried to avoid wait as much as possible, I don't want to wait 1m to see what happened with my yelpsoa-config change when I'm doing some rapid testing
Co-authored-by: Luis Pérez <[email protected]>