Specify which hooks to run via command line option #887

New Issue

Open

opened 2024-06-25 10:27:16 +00:00 by sshaikh · 1 comment

sshaikh commented 2024-06-25 10:27:16 +00:00

Copy Link

What I'd like to do and why

There are two times when I may not want hooks to run for a given config:

1. When running bespoke one off commands on demand
2. If existing hooks involve running borgmatic (to avoid recursion)

Adding a --hooks option to explicitly specify which hooks to run would help with the general case, with the specific cases of:

1. The default is to run all hooks.
2. Specifying it empty would run no hooks (or perhaps maybe using an explicit none parameter).

Other notes / implementation ideas

No response

### What I'd like to do and why There are two times when I may not want hooks to run for a given config: 1. When running bespoke one off commands on demand 2. If existing hooks involve running borgmatic (to avoid recursion) Adding a `--hooks` option to explicitly specify which hooks to run would help with the general case, with the specific cases of: 1. The default is to run all hooks. 2. Specifying it empty would run no hooks (or perhaps maybe using an explicit `none` parameter). ### Other notes / implementation ideas _No response_

sshaikh changed title from Specify hooks to run via command line option to Specify which hooks to run via command line option 2024-06-25 10:27:26 +00:00

witten commented 2024-06-25 15:42:40 +00:00

Owner

Copy Link

Seems reasonable to me! Note that you may be able to accomplish this today with one or more --override work-arounds.

Seems reasonable to me! Note that you may be able to accomplish this today with one or more [`--override`](https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#configuration-overrides) work-arounds.

witten added the

new feature area

label 2024-07-04 06:18:47 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

No results found.

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels

blocked

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

No Label

new feature area

Milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#887

No description provided.