Repository navigation
Releases: codefresh-io/disable-triggers
Release list
cf-triggers 1.2.0
cf-triggers 1.1.0
What's Changed
-
feat: add
--project-idflag in #7
This adds an ability to disable/enable pipeline triggers for the entire project. A new --project-id flag is introduced. -
feat: add custom logger with file output
This adds logs streaming to the filesystem for debugging purposes.
⚠️ Non-git trigger secrets will be streamed to the debug logs in your filesystem.
Full Changelog: 1.0.0...1.1.0
cf-triggers 1.0.0
Merge pull request #6 from codefresh-support/fix-version
- fix: fix non-git triggers recreation
Previously, non-git triggers lost any data except for event once deleted/recreated.
Now all the data is preserved.
BREAKING CHANGES: this version is not backward compatible with the pipeline annotations created by previous versions.
NB. This is the same binaries as in 0.2.1; but tagged in a correct manner that reflects breaking changes.
cf-triggers 0.2.1
Merge pull request #5 from codefresh-support/dev
fix: fix non-git triggers recreation
Previously, non-git triggers lost any data except for event once deleted/recreated. Now all the data is preserved.
cf-triggers 0.2.0
- When using with
--delete-triggersflag, Docker registry or Helm triggers lose some information when deleted/recreated.
Fixed in #0.2.1
Merge pull request #4 from codefresh-support/dev
feat: add support for CF CLI config
This adds the following flags:
--use-cfconfig[ optional, defaults tofalse] — iftrue, uses token and API host from Codefresh CLI config. If set,--tokenand--hostflags are ignored.--cfconfig[ optional ] — path to the Codefresh CLI config. Makes sense only together with--use-cfconfig. If not set, default path will be used (Windows:%USERPROFILE%\.cfconfig, Linux/Apple:$HOME/.cfconfig).--cfconfig-context[ optional ] — Codefresh CLI context to use. Makes sense only together with--use-cfconfig. If not set,current-contextwill be used.
cf-triggers 0.1.0
Merge pull request #1 from codefresh-support/dev
Add base commands