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

Generate stales only for existing services #613

Open
SteBaum opened this issue Jul 18, 2024 · 0 comments
Open

Generate stales only for existing services #613

SteBaum opened this issue Jul 18, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@SteBaum
Copy link
Contributor

SteBaum commented Jul 18, 2024

At the moment if we deploy only the basic tdp-collection but edit the vars for instance by mentioning in addition the tdp-extra collection, some components of the tdp-extra collection which do not exist on the cluster will have to be restarted or configured according to the generate_stale_sch_logs function which will always fail when launching a deployment with previously tdp plan reconfigure.

This is wrong and it should only be the other way around. if several collections are deployed we can chose to only reconfigure the services of one collection instead of all and for this reason the --collection-path option comes in handy if all collections have been defined in a path in an .env file. Therefore all potential restarted or configured services/components must exist before and have to be checked for it.

@PaulFarault PaulFarault added the bug Something isn't working label Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants