Add a new lifecycle method to providers after the stack has been initialized

[jeffmaury]

🚀 Describe the new functionality needed

As I was writing an inference provider that needs to dynamically register models while starting (not through static declaration in run.yaml), I got help from @bbrowning to inject models API but the registration fails because it has to be done in the provider constructor and thus the provider is not yet registered.

💡 Why is this needed? What if we don't build it?

To support dynamic registration of various resources related to the current provider

Other thoughts

Add a new optional lifecycle method in the provider that get called when the stack if fully initiallized

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity within 60 days. It will be automatically closed if no further activity occurs within 30 days.

[jeffmaury]

Still accurate

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity within 60 days. It will be automatically closed if no further activity occurs within 30 days.

[mattf]

@jeffmaury which inference provider?

[jeffmaury]

Podman AI Lab

[mattf]

@jeffmaury where can i find the code? is the issue that users cannot register models not in the static list? is the issue that users should not need to register models at all?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity within 60 days. It will be automatically closed if no further activity occurs within 30 days.

[github-actions[bot]]

This issue has been automatically closed due to inactivity. Please feel free to reopen if you feel it is still relevant!