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 for Carvel global namespaces #5203

Merged
merged 4 commits into from
Aug 11, 2022
Merged

Conversation

castelblanque
Copy link
Collaborator

Signed-off-by: Rafa Castelblanque rcastelblanq@vmware.com

Description of the change

This PR partially addresses bug #5200 about global namespaces handling for Carvel repositories.

Benefits

It is possible now to have Carvel package repositories correctly created in the global namespace, where global repository depends on the plugin.
Listing of repositories still aggregates both global from Helm and from Carvel.

Possible drawbacks

There is still a lot of frontend code that assumes global namespace is only the one for Helm.
We need to work in the future to refactor the global namespaces part.

Applicable issues

Additional information

Follow-up work tracked in #5202

Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
@netlify
Copy link

netlify bot commented Aug 11, 2022

Deploy Preview for kubeapps-dev canceled.

Name Link
🔨 Latest commit 96c501e
🔍 Latest deploy log https://app.netlify.com/sites/kubeapps-dev/deploys/62f51467af8218000917de60

Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Copy link
Contributor

@antgamdia antgamdia left a comment

Choose a reason for hiding this comment

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

Awesome, thanks for giving a last-minute workaround for this problem!

Comment on lines +11 to +15
// add the required polyfills (not included in webpack 5)
new NodePolyfillPlugin({
// Allow using console.log
excludeAliases: ['console'],
}),
Copy link
Contributor

Choose a reason for hiding this comment

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

Interesting... don't know how I haven't faced this problem in my local :S

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Try removing the modules folder, lock file and yarn install maybe.

* @param kubeappsConfig Kubeapps configuration
* @returns true if namespace is global
*/
export function isGlobalNamespace(namespace: string, pluginName: string, kubeappsConfig: IConfig) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Great, thanks for the refactor here!

Rafa Castelblanque added 2 commits August 11, 2022 16:23
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
@castelblanque castelblanque merged commit d2cda65 into main Aug 11, 2022
@castelblanque castelblanque deleted the 5200-global-carvel-issue branch August 11, 2022 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Global repositories handling is inconsistent - Carvel issue
3 participants