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 Kyma config from kyma-dashboard #3321

Merged
merged 10 commits into from
Sep 5, 2024

Conversation

dbadura
Copy link
Contributor

@dbadura dbadura commented Sep 2, 2024

Description

Changes proposed in this pull request:

  • copy configuration from kyma-dashboard
  • new dockerfiles for kyma-dashboard
  • adjust directories and gulp files
  • add build jobs

Related issue(s)

#3298

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
    • 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 the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 2, 2024
@kyma-bot
Copy link
Contributor

kyma-bot commented Sep 2, 2024

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

@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Sep 2, 2024
@dbadura dbadura marked this pull request as ready for review September 2, 2024 14:40
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 2, 2024
@dbadura dbadura changed the title Add Kyma config from kyma-dashboard feat: Add Kyma config from kyma-dashboard Sep 2, 2024
Copy link
Contributor

@mrCherry97 mrCherry97 left a comment

Choose a reason for hiding this comment

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

check dockerigonre

"prepare-all-dev": "ENV=dev npm run prepare-extensions && ENV=dev npm run pack-extensions && ENV=dev npm run prepare-wizards && ENV=dev npm run pack-wizards && ENV=dev npm run prepare-statics && ENV=dev npm run pack-statics",
"prepare-all-stage": "ENV=stage npm run prepare-extensions && ENV=stage npm run pack-extensions && ENV=stage npm run prepare-wizards && ENV=stage npm run pack-wizards && ENV=stage npm run prepare-statics && ENV=stage npm run pack-statics",
"prepare-all-prod": "ENV=prod npm run prepare-extensions && ENV=prod npm run pack-extensions && ENV=prod npm run prepare-wizards && ENV=prod npm run pack-wizards && ENV=prod npm run prepare-statics && ENV=prod npm run pack-statics",
"clean-all": ""
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"clean-all": ""

branches:
- main
paths:
- ".github/workflows/busola-web-build.yml"
Copy link
Contributor

Choose a reason for hiding this comment

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

should be kyma-web

pull_request_target:
types: [opened, edited, synchronize, reopened, ready_for_review]
paths:
- ".github/workflows/busola-kyma-web-build.yml"
Copy link
Contributor

Choose a reason for hiding this comment

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

should be kyma-web

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's

"prepare-all-dev": "ENV=dev npm run prepare-extensions && ENV=dev npm run pack-extensions && ENV=dev npm run prepare-wizards && ENV=dev npm run pack-wizards && ENV=dev npm run prepare-statics && ENV=dev npm run pack-statics",
"prepare-all-stage": "ENV=stage npm run prepare-extensions && ENV=stage npm run pack-extensions && ENV=stage npm run prepare-wizards && ENV=stage npm run pack-wizards && ENV=stage npm run prepare-statics && ENV=stage npm run pack-statics",
"prepare-all-prod": "ENV=prod npm run prepare-extensions && ENV=prod npm run pack-extensions && ENV=prod npm run prepare-wizards && ENV=prod npm run pack-wizards && ENV=prod npm run prepare-statics && ENV=prod npm run pack-statics",
"clean-all": ""
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"clean-all": ""

"pack-wizards": "gulp pack-wizards",
"prepare-wizards": "gulp clean-wizards && gulp get-wizards",
"lint-fix": "prettier --config ./.prettierrc --write '**/*.{ts,tsx,js,jsx,json,html,css,yaml,md}' --ignore-path ./.prettierignore",
"prepare-all-dev": "ENV=dev npm run prepare-extensions && ENV=dev npm run pack-extensions && ENV=dev npm run prepare-wizards && ENV=dev npm run pack-wizards && ENV=dev npm run prepare-statics && ENV=dev npm run pack-statics",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"prepare-all-dev": "ENV=dev npm run prepare-extensions && ENV=dev npm run pack-extensions && ENV=dev npm run prepare-wizards && ENV=dev npm run pack-wizards && ENV=dev npm run prepare-statics && ENV=dev npm run pack-statics",
"prepare-extensibility-dev": "ENV=dev npm run prepare-extensions && ENV=dev npm run pack-extensions && ENV=dev npm run prepare-wizards && ENV=dev npm run pack-wizards && ENV=dev npm run prepare-statics && ENV=dev npm run pack-statics",

{
"name": "kyma-dashboard",
"version": "1.0.0",
"description": "",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"description": "",

Comment on lines 1 to 3
export WEB_IMAGE=v20240808-1bae12fe
export BACKEND_IMAGE=v20240719-f64157c5
export LOCAL_IMAGE=v20240808-1bae12fe
Copy link
Contributor

Choose a reason for hiding this comment

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

probably that's unnecessary with this flow

Dockerfile.local.kyma Show resolved Hide resolved
kyma/.gitignore Outdated
@@ -0,0 +1,5 @@
build
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
build

@dbadura dbadura mentioned this pull request Sep 4, 2024
4 tasks
@dbadura dbadura linked an issue Sep 4, 2024 that may be closed by this pull request
11 tasks
@dbadura dbadura removed a link to an issue Sep 4, 2024
11 tasks
kyma/Makefile Outdated
Comment on lines 11 to 19
prepare-all-dev:
npm run prepare-extensibility-dev
ENV=dev make copy-config
prepare-all-stage:
npm run prepare-extensibility-stage
ENV=stage make copy-config
prepare-all-prod:
npm run prepare-extensibility-prod
ENV=prod make copy-config
Copy link
Contributor

Choose a reason for hiding this comment

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

I'll suggest to rename it, because prepare-all is suggesting, that after running this command, I have busola running, but it's only for whole configuration (extensibility + config)

Suggested change
prepare-all-dev:
npm run prepare-extensibility-dev
ENV=dev make copy-config
prepare-all-stage:
npm run prepare-extensibility-stage
ENV=stage make copy-config
prepare-all-prod:
npm run prepare-extensibility-prod
ENV=prod make copy-config
prepare-configuration-dev:
npm run prepare-extensibility-dev
ENV=dev make copy-config
prepare-configuration-stage:
npm run prepare-extensibility-stage
ENV=stage make copy-config
prepare-configuration-prod:
npm run prepare-extensibility-prod
ENV=prod make copy-config

@@ -0,0 +1,113 @@
apiVersion: operator.kyma-project.io/v1beta2
kind: ModuleTemplate
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think that these files are currently necessary, because it's only for testing part, and should be in tests directory.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Now I moved them to tests/kyma. Then those files will be adjusted when adding integration tests

@@ -0,0 +1,116 @@
apiVersion: operator.kyma-project.io/v1beta2
kind: ModuleTemplate
Copy link
Contributor

Choose a reason for hiding this comment

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

Same

@@ -0,0 +1,116 @@
apiVersion: operator.kyma-project.io/v1beta2
kind: ModuleTemplate
Copy link
Contributor

Choose a reason for hiding this comment

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

Same

Copy link
Contributor

@mrCherry97 mrCherry97 left a comment

Choose a reason for hiding this comment

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

LGTM

@kyma-bot kyma-bot added the lgtm Looks good to me! label Sep 5, 2024
@mrCherry97 mrCherry97 merged commit 4d280f5 into kyma-project:main Sep 5, 2024
12 checks passed
@dbadura dbadura deleted the kyma-config branch September 5, 2024 13:07
@dbadura dbadura mentioned this pull request Sep 12, 2024
11 tasks
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/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants