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

Remove Pilet-Only Settings When Debugging Piral Instance #670

Closed
FlorianRappl opened this issue Feb 4, 2024 · 0 comments
Closed

Remove Pilet-Only Settings When Debugging Piral Instance #670

FlorianRappl opened this issue Feb 4, 2024 · 0 comments
Labels
enhancement New feature or request tooling Concerns (third-party) tooling and services.
Milestone

Comments

@FlorianRappl
Copy link
Contributor

Description

Following the issue smapiot/piral-inspector#25 on the piral-inspector repository we should just not configure pilet-only settings when running piral debug. I think the Piral CLI can detect this and properly instruct the debug utils to communicate accordingly.

Background

Settings that do not have any impact should not be shown / available.

Discussion

This does not impact the persistence of these settings. Once they are available they should take the previously set values.

@FlorianRappl FlorianRappl added enhancement New feature or request in-implementation The item is currently being implemented. tooling Concerns (third-party) tooling and services. labels Feb 4, 2024
@FlorianRappl FlorianRappl added this to the 1.5.0 milestone Feb 4, 2024
@FlorianRappl FlorianRappl added in-testing The item is already out in preview and can be tested. and removed in-implementation The item is currently being implemented. in-testing The item is already out in preview and can be tested. labels Feb 4, 2024
FlorianRappl added a commit that referenced this issue Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tooling Concerns (third-party) tooling and services.
Projects
None yet
Development

No branches or pull requests

1 participant