Repository navigation
Rename user_data_secret_ref to user_data - #333
openshift-merge-bot[bot] merged 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
|
why not |
The fulfillment API field accepts raw user data content (cloud-init, ignition, etc.), not a secret reference. Rename to user_data to accurately describe the field and align with standard cloud provider terminology. Changes: - Proto: rename field in public and private ComputeInstanceSpec - Service: update reconciler to use HasUserData()/GetUserData() - CLI: rename --user-data-secret-ref flag to --user-data The operator CRD field userDataSecretRef is unchanged — it correctly refers to a K8s Secret created by the reconciler from the user data content. Ref: https://redhat.atlassian.net/browse/MGMT-23397 Generated with [Claude Code](https://claude.com/claude-code)
c1d2d1f to
13ef731
Compare
My initial concern with user_data is that it's quite generic - in a broad sense every field the user provides is "user data". That said, this is the established convention across cloud providers: So I'm on board — renamed to user_data. PTAL. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adriengentil, tzvatot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
user_data_secret_reftouser_datain public and private proto definitionsHasUserData()/GetUserData()--user-data-secret-refto--user-datauserDataSecretRefis unchanged — it correctly refers to a K8s SecretThe fulfillment API field accepts raw user data content (cloud-init, ignition, etc.), not a secret reference. The old name was misleading.
user_dataaligns with standard cloud provider terminology (AWS, OpenStack, GCP, KubeVirt).Ref
https://redhat.atlassian.net/browse/MGMT-23397
Test plan
Generated with Claude Code