Move the spiffe related features in its own branch #327
Labels
bug
Something isn't working
code health
Issues concerning overall code quality, safety and best practice
Because the
spiffe
dependency used for the JWT SVID authenticator is for now just agit
dependency, that prevents publishing theparsec
service crate on crates.io. Similarly for all crates usingspiffe
: parsec-client, parsec-tool, etc...For now the most sane option is to push this feature in its own
spiffe
branch on the various repos so that themaster
branch can still be published. As soon as the needed crates are published we can modify the branch and merge it back tomaster
.This should change nothing for people already using a
git
dependency on the Parsec clients or Parsec from GitHub directly.The main drawback is that if it lasts a long time, we might have to rebase the
spiffe
branch onmaster
to keep it up-to-date with developments.I plan to do it the following way:
master
to remove all thespiffe
stuffspiffe
to revert there the commit from 1.The text was updated successfully, but these errors were encountered: