[PR #1946] [MERGED] bump: r3-yamauchi/my_aws_tools v1.0.10 #1976

New Issue

2026-02-22T18:13:22-05:00

yindo commented

2026-02-22 18:13:22 -05:00

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1946
Author: @r3-yamauchi
Created: 1/23/2026
Status: ✅ Merged
Merged: 1/26/2026
Merged by: @crazywoola

Base: main ← Head: my_aws_tools

📝 Commits (1)

c2bb8af UPDATE: r3-yamauchi/my_aws_tools v1.0.10

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

📝 r3-yamauchi/my_aws_tools/my_aws_tools.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Plugin Author: r3-yamauchi
Plugin Name: my_aws_tools
Repository URL: https://github.com/r3-yamauchi/dify-my-aws-tools-plugin

2. Submission Type

New plugin submission
Version update for existing plugin

3. Description

I added two new tools to this Dify tool plugin to obtain temporary AWS credentials.
I also added aws_session_token to the parameters of each tool so that temporary AWS credentials can be used by them.
https://github.com/r3-yamauchi/dify-my-aws-tools-plugin/compare/v1.0.9...v1.0.10

4. Checklist

I have read and followed the Publish to Dify Marketplace guidelines
I have read and comply with the Plugin Developer Agreement
I confirm my plugin works properly on both Dify Community Edition and Cloud Version
I confirm my plugin has been thoroughly tested for completeness and functionality
My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

Step-by-step setup instructions
Detailed usage instructions
All required APIs and credentials are clearly listed
Connection requirements and configuration details
Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

This plugin does not collect any personal user data. It only uses the information explicitly provided by the user to access AWS. This plugin has the following characteristics:

Does not store user files permanently
Uses temporary storage only during the conversion process
Does not collect user metadata or personal information
Does not track usage patterns or user behavior
Does not require any user authentication credentials or personal identifiers

Privacy Policy

I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/1946 **Author:** [@r3-yamauchi](https://github.com/r3-yamauchi) **Created:** 1/23/2026 **Status:** ✅ Merged **Merged:** 1/26/2026 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `my_aws_tools` --- ### 📝 Commits (1) - [`c2bb8af`](https://github.com/langgenius/dify-plugins/commit/c2bb8af48673a8b111cb8820cd1da694b086cc94) UPDATE: r3-yamauchi/my_aws_tools v1.0.10 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `r3-yamauchi/my_aws_tools/my_aws_tools.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata  - **Plugin Author**: r3-yamauchi - **Plugin Name**: my_aws_tools - **Repository URL**: https://github.com/r3-yamauchi/dify-my-aws-tools-plugin ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description  I added two new tools to this Dify tool plugin to obtain temporary AWS credentials. I also added `aws_session_token` to the parameters of each tool so that temporary AWS credentials can be used by them. https://github.com/r3-yamauchi/dify-my-aws-tools-plugin/compare/v1.0.9...v1.0.10 ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection  This plugin does not collect any personal user data. It only uses the information explicitly provided by the user to access AWS. This plugin has the following characteristics: Does not store user files permanently Uses temporary storage only during the conversion process Does not collect user metadata or personal information Does not track usage patterns or user behavior Does not require any user authentication credentials or personal identifiers ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-22 18:13:22 -05:00

yindo closed this issue

2026-02-22 18:13:24 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1976