On Windows command prompts, the cf CLI binary can only be referenced as cf7 or cf8. These changes allow plugin users to override the binary name used when creating tunnels for those environments.
Also included:
Setting up pipeline for automated releases
Bump plugin version to 1.1.3
Things to check
For any logging statements, is there any chance that they could be logging sensitive data?
Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.
Changes proposed in this pull request:
Closes #69
On Windows command prompts, the cf CLI binary can only be referenced as cf7 or cf8. These changes allow plugin users to override the binary name used when creating tunnels for those environments.
Also included:
Things to check
INFOand debugging statements are written withlog.debugor similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.Security considerations
None