Skip to content

Docs: add example for create your own provider #1320

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
dreamorosi opened this issue Feb 21, 2023 · 2 comments · Fixed by #1565
Closed
1 task done

Docs: add example for create your own provider #1320

dreamorosi opened this issue Feb 21, 2023 · 2 comments · Fixed by #1565
Assignees
Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation parameters This item relates to the Parameters Utility

Comments

@dreamorosi
Copy link
Contributor

What were you searching in the docs?

The current version of the Parameters docs doesn't include an example of creating a custom provider for the utility. This section would be useful because it showcases the versatility & extensibility of the utility by allowing customers to create their own provider by extending the BaseProvider.

In doing so, customers can retrieve parameters/secrets/configs from 3rd party or unsupported services and still leverage transform and caching from Parameters.

Is this related to an existing documentation section?

This section exists in the docs of the utility in Powertools for Python.

How can we improve?

We should create a similar section that shows at least one custom provider.

Got a suggestion in mind?

N/A

Acknowledgment

  • I understand the final update might be different from my proposed suggestion, or refused.
@dreamorosi dreamorosi self-assigned this Feb 21, 2023
@dreamorosi dreamorosi converted this from a draft issue Feb 21, 2023
@dreamorosi dreamorosi added documentation Improvements or additions to documentation parameters This item relates to the Parameters Utility confirmed The scope is clear, ready for implementation labels Feb 21, 2023
@dreamorosi dreamorosi removed their assignment Feb 22, 2023
@am29d am29d self-assigned this Mar 14, 2023
@dreamorosi dreamorosi self-assigned this May 11, 2023
@dreamorosi dreamorosi moved this from Backlog to Working on it in AWS Lambda Powertools for TypeScript May 11, 2023
@dreamorosi dreamorosi linked a pull request Jun 28, 2023 that will close this issue
9 tasks
@github-project-automation github-project-automation bot moved this from Working on it to Coming soon in Powertools for AWS Lambda (TypeScript) Jun 29, 2023
@github-actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed confirmed The scope is clear, ready for implementation labels Jun 29, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jun 29, 2023

This is now released under v1.11.0 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Jun 29, 2023
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation parameters This item relates to the Parameters Utility
Projects
2 participants