sdk-for-go | Official Appwrite GO SDK | Backend As A Service library

You can do this two ways:

• custom types (to hide the MarshalJSON methods); or
• custom marshaler (using reflect to ignore any MarshalJSON methods at runtime)

For example, take these nested types:

To fix this problem, add the following ENV key/value to your lambda or application environment:

context.Context is an interface, not a method (https://pkg.go.dev/context#Context) that is why you're getting the error, you're attempting to convert nothing to that type.

Calls to the GetToken method require something that implements context.Context.

Try replacing var ctx = context.Context() with var ctx = context.Background()

Read more about context.Context here https://pkg.go.dev/context

I am going through the documentation of ListObjects function in AWS' go SDK.

Use ListObjectsV2. It behaves more or less the same, but it's an updated version of ListObjects. It's not super common for AWS to update APIs, and when they do, it's usually for a good reason. They're great about backwards compatibility which is why ListObjects still exists.

This example uses ListObjectsPages (which calls ListObjects under the hood) and claims to list all objects.

ListObjectsPages is a paginated equivalent of ListObjects, and ditto for the V2 versions which I'll describe below.

Many AWS API responses are paginated. AWS uses Cursor Pagination; this means request responses include a cursor - ContinuationToken in the case of ListObjectsV2 . If more objects exist (IsTruncated in the response), a subsequent ListObjectsV2 request content can provide the ContinuationToken to continue the listing where the first response left off.

ListObjectsV2Pages handles the iterative ListObjectsV2 requests for you so you don't have to handle the logic of ContinuationToken and IsTruncated. Instead, you provide a function that will be invoked for each "page" in the response.

So it's accurate to say ListObjectsV2Pages will list "all" the objects, but it's because it makes multiple ListObjectsV2 calls in the backend that it will list more than one page of responses.

Thus, ...Pages functions can be considered convenience functions. You should always use them when appropriate - they take away the pain of pagination, and pagination is critical to make potentially high volume api responses operable. In AWS, if pagination is supported, assume you need it - in typical cases, the first page of results is not guaranteed to contain any results, even if subsequent pages do.

Refer to this example to learn how to get an Amazon S3 object's ACL information using the AWS SDK for Go V2.

https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/gov2/s3/GetObjectAcl

region is set in ~/.aws/config.

~/.aws/config

As you can see, your function

The AWS docs state for the secretsmanager:VersionStage condition:

Filters the request based on the staging labels identified in the VersionStage parameter of a request. We recommend you do not use this key, because if you use this key, requests must pass in a staging label to compare to this policy.

Which is exactly what you experienced. You have to explicitly include the label when using this condition. It does not explain why the 'default' stage of AWSCURRENT is not working. You can find an extensive github thread discussing this issue here. The conclusion is basically that it's indeed a bit crappy how the docs formulate this, but they see no reason yet to actually update the docs.

To get the two numbers you would have to fetch them from the map. If you always know the key and you know that there will only be one element in the array you can do it like this