This message was deleted.
# flyte-support
u
This message was deleted.
a
@stale-barista-80787
Presumably I would want to add a new static client similar to the
flyte-cli
one,
That seem to be the case. According to a previous thread that worked for a CI/CD system (machine to machine auth too): https://discuss.flyte.org/t/16633322/what-is-the-recommended-way-to-authorize-the-github-actions- If it works for you please let us know, I think that section of the docs deserves a revamp
s
Thanks, that discussion looks very relevant. I'll give it a go tomorrow and see if I can get things working and report back
I finally figured it out yesterday: • I need the password/string that was bcrypted when connecting - this should be documented more clearly • I was setting
AuthType.CLIENT_CREDENTIALS
- I'm not sure passing in that enum actually works or if setting
'ClientSecret'
as a string is more correct - I need to double check that • At some point pyright "tricked" me into making the client id and secret into
bytes
- for some reason flytekit's
FlyteRemote
only ends up being able to connect if given
str
for those fields • Diffing
remote.config
against
Config.auto('some-config-that-works')
was very useful for figuring out the last bits when multiple small things where wrong, making debugging hard
a
@stale-barista-80787 thanks for confirming
• I need the password/string that was bcrypted when connecting - this should be documented more clearly
But you need this string for the "custom" client?
s
Setting the client secret to the hash did not work, I only managed to connect once I set the password as the secret
Presumably it would have worked with the flyteproppeler client if I had known what the password was, and not just the hash we stuck in our vault
a
oh got it