You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we might have a small inconsistency in how to configure callback_url vs metadata_url:
Both URLs getting passed to the provider, both URLs have some suffix: /status and /runner-registration-token when actually called.
/runner-registration-token is appended in the (openstack) provider (both, the bash version and the go version)
but the /status is appended nowhere, this has to be added directly in the configuration by the user.
I think a symmetric configuration would be much nicer, like this:
I think we might have a small inconsistency in how to configure callback_url vs metadata_url:
Both URLs getting passed to the provider, both URLs have some suffix:
/status
and/runner-registration-token
when actually called./runner-registration-token
is appended in the (openstack) provider (both, the bash version and the go version)but the
/status
is appended nowhere, this has to be added directly in the configuration by the user.I think a symmetric configuration would be much nicer, like this:
Shall I change that .. or do you prefer the way it is ?
Michael Kuhnt [email protected] Mercedes-Benz Tech Innovation GmbH (ProviderInformation)
The text was updated successfully, but these errors were encountered: