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

fix the field difference between yaml and json #1615

Merged
merged 1 commit into from
Nov 22, 2022

Conversation

24sama
Copy link
Collaborator

@24sama 24sama commented Nov 18, 2022

What type of PR is this?

/kind bug

What this PR does / why we need it:

fix the field difference between yaml and json

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Does this PR introduced a user-facing change?


Additional documentation, usage docs, etc.:


Signed-off-by: 24sama <jacksama@foxmail.com>
@ks-ci-bot ks-ci-bot added the kind/bug Categorizes issue or PR as related to a bug. label Nov 18, 2022
@ks-ci-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 24sama

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

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

@ks-ci-bot ks-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 18, 2022
@ks-ci-bot ks-ci-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 18, 2022
@pixiake
Copy link
Collaborator

pixiake commented Nov 22, 2022

/lgtm

@ks-ci-bot ks-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2022
@ks-ci-bot
Copy link
Collaborator

LGTM label has been added.

Git tree hash: c4669ad8ad0472de3f01d4fa4eefa5ee0e05f3fc

@ks-ci-bot ks-ci-bot merged commit 1c395d2 into kubesphere:master Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants