bugfix and rebuild

[jietian-sts]

Thank you for your contribution to CloudRec!

What About:

• Server (java)
• Collector (go)
• Rule (opa)

Description:

fix: 调整数据库表结构格式、前端字段初始值、默认用户初始化设置为admin角色
chore: 更新静态资源文件

Summary by Sourcery

Enhancements:

• Reformat database init SQL and add new columns and tables including email, proxy_config, tenant_rule, invite_code, and enable_inverse_selection flag.

[gemini-code-assist]

Important

Installation incomplete: to start using Gemini Code Assist, please ask the organization owner(s) to visit the Gemini Code Assist Admin Console and sign the Terms of Services.

[sourcery-ai]

Reviewer's Guide

This PR standardizes the database initialization script formatting, updates the backend user initialization to enforce the admin role, corrects a front-end form field’s default type and value, and refreshes hashed static resource references after rebuilding.

Class diagram for updated User domain logic

classDiagram
    class User {
        +String userId
        +String username
        +String roleName
        +String status
        +static User createDefaultUser()
        +static User initDefaultUser(User user)
    }

Loading

File-Level Changes

Change	Details	Files
Reformat DB init SQL indentation and alignment	Adjusted indentation and alignment of all CREATE TABLE definitions Ensured closing parentheses and default CHARSET lines are properly indented	db/init.sql
Enhance default user initialization to set admin role	Added User.initDefaultUser to assign admin role on existing user Updated SystemInitializer to call initDefaultUser when a default user exists	app/application/src/main/java/com/alipay/application/service/system/domain/User.java app/application/src/main/java/com/alipay/application/service/system/job/SystemInitializer.java
Adjust edit form field default for inverse selection	Changed enableInverseSelection from numeric (0/1) to boolean Added initialValue:false for enableInverseSelection field	client/src/pages/CloudAccount/AccountList/components/EditModalForm.tsx
Refresh static asset filenames in HTML template	Updated script src in index.html to match new hashed UMI bundle names Replaced references to old umi.*.js files with the newly generated hashes	app/bootstrap/src/main/resources/static/index.html app/bootstrap/src/main/resources/static/umi.32bf53ab.js app/bootstrap/src/main/resources/static/umi.843dc987.js

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @jietian-sts - I've reviewed your changes - here's some feedback:

• This PR contains large build artifacts (compiled Umi bundles and hashed filenames in index.html) that shouldn’t be committed; please remove generated files and rely on the build process instead.
• The SQL init script has been entirely re-indented, obscuring the actual functional changes—consider splitting pure formatting updates into a separate commit or using an automated formatter.
• Hard-coding the new Umi hash in index.html and committing the built file indicates build artifacts are managed manually; please automate versioned script injection or exclude artifacts from source control.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- This PR contains large build artifacts (compiled Umi bundles and hashed filenames in index.html) that shouldn’t be committed; please remove generated files and rely on the build process instead.
- The SQL init script has been entirely re-indented, obscuring the actual functional changes—consider splitting pure formatting updates into a separate commit or using an automated formatter.
- Hard-coding the new Umi hash in index.html and committing the built file indicates build artifacts are managed manually; please automate versioned script injection or exclude artifacts from source control.

## Individual Comments

### Comment 1
<location> `db/init.sql:310` </location>
<code_context>
-  `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT '主键',
-  `gmt_create` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间',
-  `gmt_modified` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '修改时间',
-  `associated_entity_list` varchar(1) DEFAULT NULL COMMENT '关联身份实体列表',
-  `associated_entity_number` int(11) DEFAULT NULL COMMENT '关联数量',
-  PRIMARY KEY(`id`)
</code_context>

<issue_to_address>
varchar(1) may be too restrictive for associated_entity_list.

If you need to store multiple identifiers, consider increasing the column length or switching to a type like TEXT or JSON.
</issue_to_address>

### Comment 2
<location> `client/src/pages/CloudAccount/AccountList/components/EditModalForm.tsx:324` </location>
<code_context>
                       name="enableInverseSelection"
                       tooltip={intl.formatMessage({ id: 'cloudAccount.extend.tooltip.selection.mode' })}
                       style={{ marginTop: '8px', marginBottom: 0 }}
+                      initialValue={false}
                     >
                       {intl.formatMessage({ id: 'cloudAccount.extend.title.cloud.services.inverse.selection' })}
</code_context>

<issue_to_address>
Setting initialValue to false may override existing values unintentionally.

For edit forms, ensure initialValue does not overwrite existing data. Set it only for new records or initialize from current values.
</issue_to_address>

<suggested_fix>
<<<<<<< SEARCH
                      initialValue={false}
=======
                      initialValue={rest?.enableInverseSelection ?? false}
>>>>>>> REPLACE

</suggested_fix>

### Comment 3
<location> `app/application/src/main/java/com/alipay/application/service/system/domain/User.java:82` </location>
<code_context>
         return user;
     }

+    public static User initDefaultUser(User user) {
+        user.setUserId(DEFAULT_USER_ID);
+        user.setUsername(DEFAULT_USER_ID);
+        user.setRoleName(RoleNameType.admin);
+        user.setStatus(Status.valid);
+        return user;
+    }
+
</code_context>

<issue_to_address>
initDefaultUser mutates the input User, which may lead to side effects.

Directly modifying the input User may cause issues if it's used elsewhere. Consider returning a new User or clearly documenting that the method mutates its argument.
</issue_to_address>

### Comment 4
<location> `app/application/src/main/java/com/alipay/application/service/system/job/SystemInitializer.java:136` </location>
<code_context>
         if (user == null) {
             User defaultUser = User.createDefaultUser();
             userRepository.save(defaultUser);
+        }else {
+            User.initDefaultUser(user);
+            userRepository.save(user);
         }

</code_context>

<issue_to_address>
Re-saving an existing user after mutation may overwrite other fields.

initDefaultUser modifies multiple fields, which may overwrite existing user data. To prevent data loss, update only the required fields or use a partial update.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue: varchar(1) may be too restrictive for associated_entity_list.

If you need to store multiple identifiers, consider increasing the column length or switching to a type like TEXT or JSON.

[sourcery-ai]

suggestion (bug_risk): Setting initialValue to false may override existing values unintentionally.

For edit forms, ensure initialValue does not overwrite existing data. Set it only for new records or initialize from current values.

Suggested change

	initialValue={false}
	initialValue={rest?.enableInverseSelection ?? false}

[sourcery-ai]

suggestion: initDefaultUser mutates the input User, which may lead to side effects.

Directly modifying the input User may cause issues if it's used elsewhere. Consider returning a new User or clearly documenting that the method mutates its argument.

[sourcery-ai]

issue (bug_risk): Re-saving an existing user after mutation may overwrite other fields.

initDefaultUser modifies multiple fields, which may overwrite existing user data. To prevent data loss, update only the required fields or use a partial update.

[sourcery-ai]

issue (code-quality): Don't reassign parameter - n (dont-reassign-parameters)

Explanation

Reassigning parameters can lead to unexpected behavior, especially when accessing the arguments object. It can also cause optimization issues, especially in V8.

From the Airbnb JavaScript Style Guide

[sourcery-ai]

issue (code-quality): Use const or let instead of var. (avoid-using-var)

Explanation

`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code). `let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than function-scoped.

From the Airbnb JavaScript Style Guide

[sourcery-ai]

issue (code-quality): Use const or let instead of var. (avoid-using-var)

Explanation

`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code). `let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than function-scoped.

From the Airbnb JavaScript Style Guide

[sourcery-ai]

issue (code-quality): Use const or let instead of var. (avoid-using-var)

Explanation

`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code). `let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than function-scoped.

From the Airbnb JavaScript Style Guide

[sourcery-ai]

issue (code-quality): Use const or let instead of var. (avoid-using-var)

Explanation

`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code). `let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than function-scoped.

From the Airbnb JavaScript Style Guide

[sourcery-ai]

issue (code-quality): Use const or let instead of var. (avoid-using-var)

Explanation

`const` is preferred as it ensures you cannot reassign references (which can lead to buggy and confusing code). `let` may be used if you need to reassign references - it's preferred to `var` because it is block- rather than function-scoped.

From the Airbnb JavaScript Style Guide