Closed vanny96 closed 1 month ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
This is causing quite a few issues with automation, is there any timeline on when this will be looked at?
Hi @vanny96,
Thank you so much for taking the time to contribute! Could you please elaborate on your use case for overriding the org ID? Just to clarify, tyk-sync
will automatically use the org ID from the dashboard URL provided to the CLI. For example, if tyk-sync
runs with -d http://tyk-installation.com
, it will use the org ID of the dashboard accessible via http://tyk-installation.com
.
Thanks again for your input!
@vanny96 Thank for your contribution! Starting from v2.0 Tyk Sync has become a close source product. This repository will be archived and no longer maintained. We will review all the contributions and think out fixing them in the product.
Enables the --org flag for the Update and Publish commands
Description
By just adding the flags to the cobra command configuration it should be possible to use this flag, as the existing logic is already in place
Motivation and Context
This is a useful feature and is also described by the examples, so it would be expected for it to be there.
Screenshots (if appropriate)
Types of changes
Checklist
master
!master
branch (left side). Also, it would be best if you started your change off our latestmaster
.gofmt -s -w .
go vet ./...
golangci-lint run