Add default terraform provider menu files#75
Merged
chucklever merged 5 commits intomainfrom Dec 20, 2025
Merged
Conversation
The Lambda Labs provider sources Kconfig.*.generated files that are gitignored to prevent accidental commits of user-specific API data. This means after a fresh git clone, make menuconfig fails because these files don't exist. This adds Kconfig.compute.default, Kconfig.location.default, and Kconfig.images.default files that are tracked in git and contain sensible static defaults. The Makefile target dynamic_lambdalabs_kconfig_touch now copies these defaults to the .generated files if they don't exist, rather than just creating empty files. The images default file is a placeholder since the Lambda Labs terraform provider does not currently support OS image selection. Users can run 'make cloud-config' to regenerate from the live API, but the repository now works immediately after clone without any extra steps. Generated-by: Claude AI Signed-off-by: Chuck Lever <cel@kernel.org>
The AWS provider sources Kconfig.*.generated files that are gitignored to prevent accidental commits of user-specific API data. This means after a fresh git clone, make menuconfig fails because these files don't exist. This adds Kconfig.ami.default, Kconfig.instance.default, and Kconfig.location.default files that are tracked in git and contain sensible static defaults generated from current API data. The Makefile target dynamic_aws_kconfig_touch now copies these defaults to the .generated files if they don't exist. Users can run 'make cloud-config' to regenerate from the live API, but the repository now works immediately after clone. Generated-by: Claude AI Signed-off-by: Chuck Lever <cel@kernel.org>
The Azure provider sources Kconfig.*.generated files that are gitignored to prevent accidental commits of user-specific API data. This means after a fresh git clone, make menuconfig fails because these files don't exist. This adds Kconfig.image.default, Kconfig.location.default, and Kconfig.size.default files that are tracked in git and contain sensible static defaults generated from current API data. The Makefile target dynamic_azure_kconfig_touch now copies these defaults to the .generated files if they don't exist. Users can run 'make cloud-config' to regenerate from the live API, but the repository now works immediately after clone. Generated-by: Claude AI Signed-off-by: Chuck Lever <cel@kernel.org>
The OCI provider sources Kconfig.*.generated files that are gitignored to prevent accidental commits of user-specific API data. This means after a fresh git clone, make menuconfig fails because these files don't exist. This adds Kconfig.image.default, Kconfig.location.default, and Kconfig.shape.default files that are tracked in git and contain sensible static defaults generated from current API data. The Makefile target dynamic_oci_kconfig_touch now copies these defaults to the .generated files if they don't exist. Users can run 'make cloud-config' to regenerate from the live API, but the repository now works immediately after clone. Generated-by: Claude AI Signed-off-by: Chuck Lever <cel@kernel.org>
Previously, DataCrunch had its .generated files tracked directly in git. This worked for fresh clones but meant that running 'make cloud-config' would cause the files to show as modified in git status. This converts DataCrunch to use the same .default scheme as the other cloud providers. The .generated files are now gitignored, and .default files provide the sensible static defaults. The Makefile copies from .default to .generated if the generated files don't exist. This makes DataCrunch consistent with Lambda Labs, AWS, Azure, and OCI, and prevents git pollution after regenerating from the API. Generated-by: Claude AI Signed-off-by: Chuck Lever <cel@kernel.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To ease the transition between static, hand-built Kconfig menu files and dynamically constructed Kconfig menu files, introduce default menu files that are available immediately after a "git clone" of the kdevops repository. These are checked into git and tracked by source control. As part of "make menuconfig", there's now an intermediate make target that copies these defaults to the .generated file names if they don't already exist.