This repository has been archived by the owner on May 6, 2021. It is now read-only.
Allow the idler to exclude some deployments from idling #232
Assignees
Milestone
Comments
|
@pradeepitm12 Any updates on this issue? |
pradeepitm12
pushed a commit
to pradeepitm12/fabric8-jenkins-idler
that referenced
this issue
Jan 28, 2019
pradeepitm12
pushed a commit
to pradeepitm12/fabric8-jenkins-idler
that referenced
this issue
Jan 29, 2019
pradeepitm12
pushed a commit
to pradeepitm12/fabric8-jenkins-idler
that referenced
this issue
Jan 30, 2019
…ices#232 Resolves - fabric8-services#232 Incorporate comments
pradeepitm12
pushed a commit
to pradeepitm12/fabric8-jenkins-idler
that referenced
this issue
Feb 19, 2019
Adds a new api to enable/disable idler for a set of users.
Idler can be disbled for a user as follows
```
curl -H "Content-Type: application/json" \
-X POST \
--data '{"disable":["pradkuma-preview2"],"enable":[]}' \
http://idler:8080/api/idler/userstatus/
```
Use `GET` to fetch the list of currently idled users
```
curl http://idler:8080/api/idler/userstatus/
```
Resolves
- fabric8-services#232
|
@pradeepitm12 if done, could we close this? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to have a way to exclude some deployments from being idled. This is useful when we need to troubleshoot a jenkins instance running in production where we cant easily reproduce the problem in staging.
For instance, if the idler sees a specific annotation on the DC, skip idling it and dont scale it down.
One more reason to do this is that development of idler requires connecting to prod-preview and restricting local idler to a single user using the
JC_FIXED_UUIDenv var. Since an idler is already running in prod-preview it often handles the openshift event causing more than the actual dc events to be generated.Thus the proposal is to allow idler to ignore certain users on prod-preview perhaps by using the feature-toggle-service (see related discussion)
Also related: #83
The text was updated successfully, but these errors were encountered: