Skip to content
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

Upgrade Provider - Create/Update provider design, readme, contributing and support docs #50

Closed
kmoe opened this issue Aug 13, 2021 · 2 comments · Fixed by #114
Closed
Assignees
Milestone

Comments

@kmoe
Copy link
Member

kmoe commented Aug 13, 2021

Maintenance of the standard library providers prioritises stability and correctness relative to the provider's intended feature set. Create a design document describing this feature set, and any other design considerations which influence the architecture of the provider and what can and cannot be added to it.

As part of the utility provider upgrade guidance in the form of CONTRIBUTING.md, DESIGN.md, README.mdandSUPPORT.md` either needs to be added or updated. There are examples in the tls provider:

@bendbennett bendbennett changed the title Create provider design doc Upgrade Provider - Create/Update provider design, readme, contributing and support docs Jul 11, 2022
@bendbennett bendbennett added this to the v0.8.0 milestone Jul 11, 2022
@SBGoods SBGoods self-assigned this Aug 3, 2022
@SBGoods
Copy link
Contributor

SBGoods commented Aug 4, 2022

In order to keep the scope of this issue relatively small, I've created a separate issue for creating the design doc. See #113.

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants