github/dokku
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
12,537 Commits 2 Branches 347 Tags
ee467e679357f0c6474d41e15d2fccd062bf92df
Commit Graph

20 Commits

Author SHA1 Message Date
Jose Diaz-Gonzalez
b4f3741ac7 fix: properly handle NoAppsExist in network:rebuild-all and buildpacks:set 
Refs #6815
 2025-03-08 23:49:40 -05:00
Jose Diaz-Gonzalez
e1af6ad1f9 fix: ensure all report subcommands exit 0 when there is no app 
Closes #7454
 2025-02-02 01:37:20 -05:00
Jose Diaz-Gonzalez
bb5ab0a777 refactor: use CallPlugnTrigger instead of PlugnTrigger 
Refs #6422
 2024-03-14 03:11:37 -04:00
Jose Diaz-Gonzalez
9cb54950fc fix: correct issue where removing by index failed due to incorrect input validation 
Closes #6657
 2024-03-13 06:53:05 -04:00
Vincent Boisard
d7dfc5d30b Purge cache for all apps when calling buildpacks:set-property with --global flag 2022-01-13 19:42:11 +01:00
Jose Diaz-Gonzalez
033b0952dd feat: allow formatting :report command output as json 2021-02-01 22:23:30 -05:00
Jose Diaz-Gonzalez
f81c802ecc refactor: rename command to :set-property 
This will allow us to set other property values for the buildpacks plugin.
 2021-01-23 18:17:40 -05:00
Jose Diaz-Gonzalez
7caa95b3f3 feat: conditionally execute the post-stack-set call 
If the value does not change, then we should not trigger the command
 2021-01-23 17:40:53 -05:00
Jose Diaz-Gonzalez
b5c85ad5be chore: rename stacks-set to stack-set 
You can only set one stack...
 2021-01-23 17:40:50 -05:00
Jose Diaz-Gonzalez
bad90b2b1d feat: add ability to manage stacks on an app or global level 
The previous lever for manipulating this was the DOKKU_IMAGE environment variable. While this is all well and good, it only works for CNB and is yet another `DOKKU_*` environment variable that need not exist.

While this does not add support for manipulating the CNB stack just yet, the groundwork is set for the future.

Closes #4306
 2021-01-23 16:19:12 -05:00
Jose Diaz-Gonzalez
ffa303092f feat: add app name verification to all golang plugins 
Moving verification of input to the earliest place is the best way to decrease the need to validate this further downstream.

Additionally, some of the existing checks were.... lacking :)
 2020-12-27 15:14:11 -05:00
Jose Diaz-Gonzalez
1439e8b30b hack: parse out the info flags for report subcommands separately 
pflag doesn't ignore unspecified arguments, so they must be parsed out separately first.
 2020-12-21 01:36:59 -05:00
Jose Diaz-Gonzalez
6636c48838 feat: simplify flag parsing in buildpacks plugin 
Commands should be written such that they take arguments as is.
 2020-05-29 01:59:50 -04:00
Jose Diaz-Gonzalez
93225ada48 feat: add proper support for various buildpack urls 
Transform the urls to the correct values when necessary, and validate them otherwise.

Closes #3923
 2020-04-07 00:17:03 -04:00
Jose Diaz-Gonzalez
bd47c76d26 refactor: move private buildpacks function to functions.go 2020-03-10 14:12:24 -04:00
Jose Diaz-Gonzalez
26e8524ae5 refactor: surface errors when running reports 2020-02-22 06:40:24 -05:00
Jose Diaz-Gonzalez
6a7d2e5252 refactor: decrease compile time for golang plugins 
This change refactors the compiled golang plugins into 3 distinct binaries:

- commands: already existing
- subcommands/subcommands: entrypoint into all subcommands
- triggers: entrypoint into all triggers

It then further symlinks triggers and subcommands to the built binaries. This results in both a much faster build process as well as smaller package size.
 2019-09-15 19:15:08 -04:00
Jose Diaz-Gonzalez
d3d426a8d9 tests: add functional tests for buildpacks plugin 2019-03-05 21:41:23 -05:00
Jose Diaz-Gonzalez
3670d7efcd fix: correct fmt.Errorf violations 2019-03-05 21:41:23 -05:00
Jose Diaz-Gonzalez
887c1d4254 feat: implement buildpacks plugin 
This will allow users to specify buildpacks outside of a git repository.

Note that this does not override any specified `BUILDPACK_URL`.

Closes #3256
 2019-03-05 21:41:23 -05:00