-
Notifications
You must be signed in to change notification settings - Fork 2.7k
WIP chore(provider): inline providers first steps #5312
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
base: master
Are you sure you want to change the base?
WIP chore(provider): inline providers first steps #5312
Conversation
Signed-off-by: ivan katliarchuk <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: ivan katliarchuk <[email protected]>
/label tide/merge-method-squash |
Signed-off-by: ivan katliarchuk <[email protected]>
Signed-off-by: ivan katliarchuk <[email protected]>
Signed-off-by: ivan katliarchuk <[email protected]>
@ivankatliarchuk It's a good step ! The part |
Signed-off-by: ivan katliarchuk <[email protected]>
Description
It's most likely a good idea to inline providers, this will help to simplify operational support, and add support for
--provider-<flag>
instead of--<provider-name>-<flag>
and similarIn this pull request
custom TTL
constansts todefaultTTL
Ideally providers should support
Relates
follow-up:
Checklist