In `AssumeRoleWithWebIdentity` requests, the RoleArn form paramter is
designated to specify the role to be assumed. It is crucial to note that
the correct key is RoleArn, not RoleARN.
When I used the "RoleARN" form key instead of "RoleArn," I encountered
an error similar to the following:
```xml
<ErrorResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/"><Error><Type></Type><Code>InvalidParameterValue</Code><Message>Role arn:minio:iam:::role/dummy-internal does not exist</Message></Error><RequestId>XXX</RequestId></ErrorResponse>
```
Despite this, certain documentation erroneously employs RoleARN. To
rectify this inconsistency, I have replaced the instances of RoleARN
with the correct RoleArn. However, for other documents that use RoleARN
without specifying the form parameter, no modifications have been made.
Ref:
ba245c6c46/cmd/sts-handlers.go (L50C2-L50C12)
Now that I know why. The additional context to do go get in a project
directory doesn't fit in the format of this page, but it's in the
Quickstart update.
The URL for the Java SDK JAR is a static string + the SDK version
number. Use the existing `java-sdk-version` value to construct the
correct URL.
C++ doesn't have any releases, so there's no Quickstart to generate.
Move it to the bottom and only link to GitHub and the Doxygen reference
page.
Staged
http://192.241.195.202:9000/staging/java-sdk-jar-url/linux/developers/minio-drivers.html
Small cleanup of the main SDK index page.
[x] More clearly link to respective Quickstarts, API references, and
GitHub repos.
[x] Reorder more-or-less by popularity.
Non-goals:
Validating the install steps provided (except replace `go get` with `go
install ...@version`)
Staged:
http://192.241.195.202:9000/staging/main-sdk-page/linux/developers/minio-drivers.html
Closes#898
- Adds a short section on synchronous vs asynchronous bucket
notifications
- Adds a note on specific configs which now return redacted data on `mc
admin config get`
- Found a few new webhook lambda envvars to add
Object Lambda functions to transform objects via a webhook. Expand and
refine the developer docs from
c4d71bc1a5/docs/lambda/README.md
into a new page in the user documentation.
Staged
http://192.241.195.202:9000/staging/DOCS-754/linux/html/developers/transforms-with-object-lambda.html
Notes for reviewers:
In addition to the items noted in inline comments, some general things
to confirm:
* Accurate usage/terminology? Is this how we talk about the relevant
topics?
* Any technical points that need more/more correct detail?
* What would someone need to know to go from trying this dev example to
having a real function in their production environment?
[x] Add new docs page in Developers
[x] Add envars to envar list
Fixes https://github.com/minio/docs/issues/754
A few minor cleanups:
- Removing the SDK markdown docs from git tracking. They're already
tracked in the SDK directories, we don't need to do that twice
- Cleaning up the builds, as only Linux needs to build out the SDK docs
at this time
- Fixing build-docs.sh to build the SDK docs with Linux (so we get
proper version numbers). Means we have to build Linux with SYNC_SDK=TRUE
on the server to pull in the SDK docs (otherwise they will all be
empty).
Tested locally and everything seems to work just fine. Will see what
happens when it goes live, but I figured I'd ask for @harshavardhana 's
thoughts since they know more about the build server script process than
I do.
This adds content to the three stub files.
Corrects the Makefile for incorrect importing of Javascript docs into the Haskell folder.
Corrects community Slack URLs to point to slack.min.io.
This commit also generally cleans up the Installation docs and uses /includes/<platform>/steps-*.rst as a pattern for storing platform-specific tutorials within a single root URL.
Finally, due to API rate limits, this commit adds some Makefile magic to allow skipping of sync'ing dependencies. Pass `make BUILD_DEPENDENCIES=FALSE <platform>` to skip building any deps and use what is already in the branch.
