fb31761bad
Create an API generator middleware for being able to hook the new satellite admin authorization in the endpoints. The commit fixes a bug found in the API generator that caused that fields of types of the same package of the generated code where wrongly added. Concretely: - The package matching was missing in the function middlewareFields, hence it was generating code that referenced types with the package name. - middlewareFields function was not adding the pointer symbol (*) when the type was from the same package where the generated code is written. There is also an accidental enhancement in the API generator because I thought that the bug commented above corresponded to it, rather than removing it, I though that was worthwhile to keep it because it was already implemented. This enhancement allows to use fields in the middleware with packages whose last path part contains `-` or `.`, using a package rename in the import statement. Change-Id: Ie98b303226a8e8845e494f25054867f95a283aa0 |
||
---|---|---|
.github | ||
certificate | ||
cmd | ||
crashcollect | ||
docs | ||
installer/windows | ||
multinode | ||
private | ||
resources | ||
satellite | ||
scripts | ||
storagenode | ||
testsuite | ||
versioncontrol | ||
web | ||
.dockerignore | ||
.earthlyignore | ||
.gitattributes | ||
.gitignore | ||
.gitreview | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
DEVELOPING.md | ||
docker-compose.tests.yaml | ||
Earthfile | ||
go.mod | ||
go.sum | ||
Jenkinsfile | ||
Jenkinsfile.premerge | ||
Jenkinsfile.public | ||
Jenkinsfile.verify | ||
Jenkinsfile.versions | ||
LICENSE | ||
MAINTAINERS.md | ||
Makefile | ||
monkit.lock | ||
proto.lock | ||
README.md |
Storj V3 Network
Storj is building a distributed cloud storage network. Check out our white paper for more info!
Storj is an S3-compatible platform and suite of distributed applications that allows you to store data in a secure and distributed manner. Your files are encrypted, broken into little pieces and stored in a global distributed network of computers. Luckily, we also support allowing you (and only you) to retrieve those files!
Table of Contents
Contributing to Storj
All of our code for Storj v3 is open source. If anything feels off, or if you feel that some functionality is missing, please check out the contributing page. There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.
A Note about Versioning
While we are practicing semantic versioning for our client libraries such as uplink, we are not practicing semantic versioning in this repo, as we do not intend for it to be used via Go modules. We may have backwards-incompatible changes between minor and patch releases in this repo.
Start using Storj
Our wiki has documentation and tutorials. Check out these three tutorials:
License
This repository is currently licensed with the AGPLv3 license.
For code released under the AGPLv3, we request that contributors sign our Contributor License Agreement (CLA) so that we can relicense the code under Apache v2, or other licenses in the future.
Support
If you have any questions or suggestions please reach out to us on our community forum or file a ticket at https://support.storj.io/.