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

feat: Add ability to expand manually added module to kyma #3676

Merged
merged 5 commits into from
Feb 13, 2025

Conversation

dbadura
Copy link
Contributor

@dbadura dbadura commented Feb 6, 2025

Description

Changes proposed in this pull request:

  • If modules is added with custom resource, busola tries to find ModuleTemplate to display ModuleResource

Related issue(s)
Closes #3624

Definition of done

  • The PR's title starts with one of the following prefixes:
    • feat: A new feature
    • fix: A bug fix
    • docs: Documentation only changes
    • refactor: A code change that neither fixes a bug nor adds a feature
    • test: Adding tests
    • revert: Revert commit
    • chore: Maintainance changes to the build process or auxiliary tools, libraries, workflows, etc.
  • Related issues are linked. To link internal trackers, use the issue IDs like backlog#4567
  • Explain clearly why you created the PR and what changes it introduces
  • All necessary steps are delivered, for example, tests, documentation, merging

@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 6, 2025
@dbadura dbadura changed the title feata: Add ability to expand manually added module to kyma feat: Add ability to expand manually added module to kyma Feb 6, 2025
@@ -382,6 +391,7 @@ export default function KymaModulesList({
};

const getAssociatedResources = () => {
// TODO: tutaj leci undefined dla 1 i 3 argumentu
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice TODO. How about fixing it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be fixed now.

const isExtension = !!findExtension(resource?.resource?.kind);
const moduleStatus = findStatus(kymaResource, resourceName);
const moduleStatus = resource;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's no longer assigned to findStatus maybe it will be better to remove this variable and use resource directly

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed.

@kyma-bot kyma-bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 12, 2025
@kyma-bot kyma-bot added the lgtm Looks good to me! label Feb 13, 2025
@dbadura dbadura merged commit 54f9f08 into kyma-project:main Feb 13, 2025
18 checks passed
@dbadura dbadura deleted the manual-modules-navigable branch February 13, 2025 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make Module CR navigable on module list also in case of modules operated with customResourcePolicy: Ignore
4 participants