Skip to content
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.

Disabling a single Bucket #115

Closed
tknerr opened this issue Jul 17, 2014 · 3 comments
Closed

Disabling a single Bucket #115

tknerr opened this issue Jul 17, 2014 · 3 comments
Labels
enhancement ignored

Comments

@tknerr
Copy link

tknerr commented Jul 17, 2014

Is it possible to disable a single bucket?

E.g. to keep config.cache.auto_detect = true but disable / blacklist a specific bucket which makes problems?
@tknerr
Copy link
Author

tknerr commented Jul 17, 2014

Concrete use case: I want to use caching for everything except :apt_lists because it makes problems (see #113, #106).

So right now I can only turn off auto-detection and enable the desired buckets afaik.

For one its more effort and you lose the super useful auto-detection feature, and on the other hand it caching the omnibus packages will only work if auto_detect = true

@fgrehm
Copy link
Owner

fgrehm commented Jul 17, 2014

Tagged as an enhancement

@fgrehm fgrehm modified the milestone: v1.0 Jul 20, 2014
@fgrehm fgrehm mentioned this issue Sep 24, 2014
Closed
@fgrehm fgrehm mentioned this issue Feb 4, 2015
Closed
electrofelix added a commit to electrofelix/vagrant-cachier that referenced this issue Feb 9, 2015
@electrofelix
Allow explicit disabling of auto detected buckets
4d43be5 
Add config option to identify buckets that should not be automatically
enabled with using `config.cache.auto_detect = true`.

After turning on the auto_detect behaviour, with this change you can
now explicitly disable any bucket type through your Vagrantfile e.g.
`config.cache.disable = :chef_gem`.

Fixes fgrehm#115
electrofelix added a commit to electrofelix/vagrant-cachier that referenced this issue Feb 9, 2015
@electrofelix
Allow explicit disabling of auto detected buckets
2eb1f33 
Add config option to identify buckets that should not be automatically
enabled with using `config.cache.auto_detect = true`.

After turning on the auto_detect behaviour, with this change you can
now explicitly disable any bucket type through your Vagrantfile e.g.
`config.cache.disable = :chef_gem`.

Fixes fgrehm#115
@electrofelix electrofelix mentioned this issue Feb 9, 2015
Closed
electrofelix added a commit to electrofelix/vagrant-cachier that referenced this issue Feb 10, 2015
@electrofelix
Allow explicit disabling of auto detected buckets
ce88219 
Add config option to identify buckets that should not be automatically
enabled with using `config.cache.auto_detect = true`.

After turning on the auto_detect behaviour, with this change you can
now explicitly disable any bucket type through your Vagrantfile e.g.
`config.cache.disable = :chef_gem`.

Fixes fgrehm#115
electrofelix added a commit to electrofelix/vagrant-cachier that referenced this issue Mar 3, 2015
@electrofelix
Allow explicit disabling of auto detected buckets
7807d2b 
Add config option to identify buckets that should not be automatically
enabled with using `config.cache.auto_detect = true`.

After turning on the auto_detect behaviour, with this change you can
now explicitly disable any bucket type through your Vagrantfile e.g.
`config.cache.disable = :chef_gem`.

Fixes fgrehm#115
@fgrehm fgrehm added the ignored label Nov 22, 2022
@fgrehm
Copy link
Owner

fgrehm commented Nov 22, 2022

Hey, sorry for the silence here but this project is looking for maintainers 😅

As per #193, I've added the ignored label and will close this issue. Thanks for the interest in the project and LMK if you want to step up and take ownership of this project on that other issue 👋

@fgrehm fgrehm closed this as completed Nov 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement ignored
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow explicit disabling of auto detected buckets electrofelix/vagrant-cachier
2 participants
@fgrehm @tknerr