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

Requirement 2.5.2 might not be relevant anymore #270

Open
fabriziodemaria opened this issue Sep 5, 2024 · 1 comment
Open

Requirement 2.5.2 might not be relevant anymore #270

fabriziodemaria opened this issue Sep 5, 2024 · 1 comment
Labels
question Further information is requested

Comments

@fabriziodemaria
Copy link
Contributor

Link to requirement here.
It reads:

After a provider's shutdown function has terminated successfully, the provider's state MUST revert to its uninitialized state.
If a provider requires initialization, once it's shut down, it must transition to its initial NOT_READY state. Some providers may allow reinitialization from this state. Providers not requiring initialization are assumed to be ready at all times.

According to recent spec changes, the Provider Status is now meant to be maintained by the SDK, so it's not a Provider's responsibility to transition to NOT_READY state.

@lukas-reining
Copy link
Member

If a provider requires initialization, once it's shut down, it must transition to its initial NOT_READY state. Some providers may allow reinitialization from this state. Providers not requiring initialization are assumed to be ready at all times.

Mh, I think the content here is right but has to be adjusted to "the clients status accessor" instead of "providers status".
But it is a good point, I think we should adjust this and move it to section one.
Does that make sense?

@beeme1mr beeme1mr added the question Further information is requested label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants