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

Allow creating Kura component configurations #4165

Open
reda-alaoui opened this issue Jan 3, 2025 · 2 comments · May be fixed by #4166
Open

Allow creating Kura component configurations #4165

reda-alaoui opened this issue Jan 3, 2025 · 2 comments · May be fixed by #4166

Comments

@reda-alaoui
Copy link

reda-alaoui commented Jan 3, 2025

Is your feature request related to a problem? Please describe.

As of today, there is no way to create a component configuration on Kura via Kapua.

Describe the solution you'd like

I'd like to have a button on the Kapua admin console allowing to do that. But on the Kura side, it looks like the feature is supported by CONF-V2, not CONF-V1. Looks like Kapua is currently using CONF-V1 to alter Kura configuration.

So I think the first step is to migrate to CONF-V2 ?

Describe alternatives you've considered
Praying :P

@reda-alaoui reda-alaoui changed the title Move from Kapua CONF-V1 to Kapua CONF-V2 Allow creating Kura component configuration Jan 4, 2025
@reda-alaoui reda-alaoui changed the title Allow creating Kura component configuration Allow creating Kura component configurations Jan 4, 2025
@reda-alaoui reda-alaoui linked a pull request Jan 5, 2025 that will close this issue
@Agnul97
Copy link
Contributor

Agnul97 commented Jan 9, 2025

Are you really sure that you need CONF-V2 for your goals? maybe with V1 it is sufficient. Anyway, you can try using this endpoint "/{scopeId}/devices/{deviceId}/requests" which allows you to use whatever device management app, including the CONF-V2, provided the correct request body. Its not included as a button in the console but as a workaround you can try using the api

@reda-alaoui
Copy link
Author

Are you really sure that you need CONF-V2 for your goals? maybe with V1 it is sufficient.

According to my research, V1 doesn't expose this feature.

Anyway, you can try using this endpoint "/{scopeId}/devices/{deviceId}/requests" which allows you to use whatever device management app, including the CONF-V2, provided the correct request body. Its not included as a button in the console but as a workaround you can try using the api

Yes that's what I already do in some cases. But I need it on the console to allow anyone to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants