-
-
Notifications
You must be signed in to change notification settings - Fork 1
Add secondary Nix-based build system #212
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
Conversation
I have tested a bit against darwin/macOS and the basic principles still work (using a remote Linux builder). However, there are some surrounding papercuts that need to be resolved for that setup to be usable (for example, we need to configure the target platform, |
Added product-config properties to docker image. CHanged nix command in tiltfile
In stackabletech/operator-templating#212 we are planning to add a more developer friendly workflow for building and deploying artifacts to Kubernetes during development. This workflow uses crate2nix, which uses rustc directly and does not provide all environment variables required by the built crate we use (see nix-community/crate2nix#158). The content of these PR are the fixes needed to work around those limitations.
…the docs. For implementation, see: - stackabletech/operator-templating#212 - stackabletech/hdfs-operator#312
- Only add properties.yaml if it exists - Correctly calculate port for Tilt instead of using string concatenation
addressed comments @nightkr |
LGTM now. I can't approve since it was my PR originally. |
I can :) |
Want the honours of merging/starting the rollout? :P |
I only did some drudge work here, its your brainchild :) |
Should we try and get stackabletech/hdfs-operator#312 in as well, to give people something to test with? |
# Description In stackabletech/operator-templating#212 we are planning to add a more developer friendly workflow for building and deploying artifacts to Kubernetes during development. This workflow uses crate2nix, which uses rustc directly and does not provide all environment variables required by the built crate we use (see nix-community/crate2nix#158). The content of these PR are the fixes needed to work around those limitations.
# Description In stackabletech/operator-templating#212 we are planning to add a more developer friendly workflow for building and deploying artifacts to Kubernetes during development. This workflow uses crate2nix, which uses rustc directly and does not provide all environment variables required by the built crate we use (see nix-community/crate2nix#158). The content of these PR are the fixes needed to work around those limitations. Co-authored-by: Sönke Liebau <[email protected]>
…the docs (#360) * Adds explanation of crate2nix and tilt based development workflow to the docs. For implementation, see: - stackabletech/operator-templating#212 - stackabletech/hdfs-operator#312 Co-authored-by: Natalie <[email protected]>
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details Co-authored-by: Razvan-Daniel Mihai <[email protected]>
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details
see stackabletech/operator-templating#212 for more details
This won't be used for prod builds (for now), but allows Nix to cache library builds, which gives us much faster feedback loops during development (for operators that need to run inside of the K8s cluster).
This is based on (and obsoletes) the Nix build system from secret-op and listener-op.
This requires some minor changes to the operator, such as the following for Airflow: