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

CONSOLE-3431: Allow building dynamic plugins without any exposed modules #12530

Conversation

vojtechszocs
Copy link
Contributor

@vojtechszocs vojtechszocs commented Feb 3, 2023

Fixes CONSOLE-3431

This is a backport of a fix from openshift/dynamic-plugin-sdk#199.

How to verify this fix:

# [1] Update Console dependencies and rebuild its plugin SDK
cd /path/to/console/frontend
yarn install

# [2] Simulate a use case where a plugin has no exposed modules
cd /path/to/console/dynamic-demo-plugin
rm -rf node_modules/@openshift-console && yarn install --check-files
# Manual step: edit package.json and remove consolePlugin.exposedModules
CONSOLE_PLUGIN_SKIP_EXT_VALIDATOR=true yarn build-dev

The demo plugin should now build without errors even if it doesn't provide any exposed modules.

@openshift-ci openshift-ci bot added component/sdk Related to console-plugin-sdk approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 3, 2023
@vojtechszocs
Copy link
Contributor Author

/retest

2 similar comments
@vojtechszocs
Copy link
Contributor Author

/retest

@vojtechszocs
Copy link
Contributor Author

/retest

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2023
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 22, 2023
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 22, 2023
@vojtechszocs vojtechszocs force-pushed the support-empty-exposed-modules branch from 30235a8 to 90b0ede Compare July 7, 2023 15:45
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 7, 2023
@vojtechszocs vojtechszocs changed the title Allow building dynamic plugins without any exposed modules CONSOLE-3431: Allow building dynamic plugins without any exposed modules Jul 7, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 7, 2023

@vojtechszocs: This pull request references CONSOLE-3431 which is a valid jira issue.

In response to this:

Fixes CONSOLE-3431

This is a backport of a fix from openshift/dynamic-plugin-sdk#199.

How to verify this fix:

# [1] Update Console dependencies and rebuild its plugin SDK
cd /path/to/console/frontend
yarn install

# [2] Simulate a use case where a plugin has no exposed modules
cd /path/to/console/dynamic-demo-plugin
# Edit package.json and remove consolePlugin.exposedModules
CONSOLE_PLUGIN_SKIP_EXT_VALIDATOR=true yarn build-dev

The demo plugin should now build without errors even if it doesn't provide any exposed modules.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 7, 2023
@spadgett
Copy link
Member

spadgett commented Jul 7, 2023

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 7, 2023
Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

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

Sorry I missed this.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spadgett, vojtechszocs

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

@vojtechszocs
Copy link
Contributor Author

/retest

@vojtechszocs
Copy link
Contributor Author

This removes the plugin build constraint that each plugin must provide at least one exposed module.

No impact for existing plugins.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 10, 2023

@vojtechszocs: This pull request references CONSOLE-3431 which is a valid jira issue.

In response to this:

Fixes CONSOLE-3431

This is a backport of a fix from openshift/dynamic-plugin-sdk#199.

How to verify this fix:

# [1] Update Console dependencies and rebuild its plugin SDK
cd /path/to/console/frontend
yarn install

# [2] Simulate a use case where a plugin has no exposed modules
cd /path/to/console/dynamic-demo-plugin
rm -rf node_modules/@openshift-console && yarn install --check-files
# Manual step: edit package.json and remove consolePlugin.exposedModules
CONSOLE_PLUGIN_SKIP_EXT_VALIDATOR=true yarn build-dev

The demo plugin should now build without errors even if it doesn't provide any exposed modules.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vojtechszocs
Copy link
Contributor Author

Requesting approvals:

QE Approver:

/assign @yanpzhan
Docs Approver:

/assign @ahardin-rh
PX Approver:
/assign @RickJWagner

No impact on existing plugins.

@RickJWagner RickJWagner removed their assignment Jul 11, 2023
@RickJWagner
Copy link

/label px-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Jul 11, 2023
@yanpzhan
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 12, 2023
Copy link
Contributor

@opayne1 opayne1 left a comment

Choose a reason for hiding this comment

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

/label docs-approved

@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Jul 17, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 18, 2023

@vojtechszocs: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit 39cefbe into openshift:master Jul 18, 2023
6 checks passed
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. component/sdk Related to console-plugin-sdk docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants