Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

Rename user_data_secret_ref to user_data - #333

Merged
openshift-merge-bot[bot] merged 1 commit into
osac-project:mainfrom
tzvatot:feature/rename-cloudinit-mgmt-23397
Mar 19, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
osac-project:mainfrom
tzvatot:feature/rename-cloudinit-mgmt-23397

Conversation

@tzvatot

@tzvatot tzvatot commented Mar 18, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Rename user_data_secret_ref to user_data in public and private proto definitions
  • Update reconciler to use HasUserData() / GetUserData()
  • Rename CLI flag --user-data-secret-ref to --user-data
  • The operator CRD field userDataSecretRef is unchanged — it correctly refers to a K8s Secret

The fulfillment API field accepts raw user data content (cloud-init, ignition, etc.), not a secret reference. The old name was misleading. user_data aligns with standard cloud provider terminology (AWS, OpenStack, GCP, KubeVirt).

Ref

https://redhat.atlassian.net/browse/MGMT-23397

Test plan

  • Unit tests pass
  • Integration tests

Generated with Claude Code

@openshift-ci

openshift-ci Bot commented Mar 18, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@adriengentil

adriengentil commented Mar 18, 2026 •

Copy link
Copy Markdown
Contributor

why not user_data instead of cloud_init? It's a common name in cloud providers, and it matches the same name in ComputeInstance CR. Also we can pass ignition through the user data, it's not specific to cloud init.

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)
@tzvatot
tzvatot force-pushed the feature/rename-cloudinit-mgmt-23397 branch from c1d2d1f to 13ef731 Compare March 18, 2026 17:00
@tzvatot tzvatot changed the title Rename user_data_secret_ref to cloud_init Rename user_data_secret_ref to user_data Mar 18, 2026
@tzvatot

tzvatot commented Mar 18, 2026 •

Copy link
Copy Markdown
Contributor Author

why not user_data instead of cloud_init? It's a common name in cloud providers, and it matches the same name in ComputeInstance CR. Also we can pass ignition through the user data, it's not specific to cloud init.

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.

@openshift-ci

openshift-ci Bot commented Mar 19, 2026

Copy link
Copy Markdown

[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

Details Needs approval from an approver in each of these files:
  • OWNERS [adriengentil,tzvatot]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants