Skip to content
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

chore(app/spire): make spire compilation possible for non-linux targets #3627

Merged
merged 2 commits into from
Feb 21, 2025

Conversation

zaharidichev
Copy link
Member

At the moment the fact that SPIRE uses Unix domain sockets prevents us from building
the proxy for non-unix targets. This PR adds special casing that allows us to build for
these targets but makes the spire client fail at runtime. Non-unix support for Spire shall
be introduced at a later stage.

Signed-off-by: Zahari Dichev [email protected]

@zaharidichev zaharidichev requested a review from a team as a code owner February 20, 2025 09:59
@@ -17,17 +17,27 @@ pub struct Config {

// Connects to SPIRE workload API via Unix Domain Socket
pub struct Client {
#[allow(dead_code)]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use cfg_attr to only mark this type as dead_code for not(target_os = "linux")?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

makes sense, will address

Signed-off-by: Zahari Dichev <[email protected]>
Copy link
Collaborator

@cratelyn cratelyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks 🙂

@olix0r olix0r merged commit fc4efc9 into main Feb 21, 2025
15 checks passed
@olix0r olix0r deleted the zd/spire-compile-non-linux branch February 21, 2025 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants