Skip to content

Conversation

@DavidFair
Copy link
Collaborator

Fixes various unescaped vars in shellcheck which are currently failing the CI.
This doesn't address the remaining warnings about usage of sudo, as we can combine "usermod -aG" with "newgrp" to avoid having to restart the session

Fixes various unescaped vars in shellcheck which are currently failing
the CI.
This doesn't address the remaining warnings about usage of sudo, as we
can combine "usermod -aG" with "newgrp" to avoid having to restart the
session
@DavidFair DavidFair added the bug Something isn't working label Jan 8, 2026
@DavidFair
Copy link
Collaborator Author

@khalford Could you pick up the newgrp bit to complete this? I'll review and test both parts once that's done

Using tee here as sudo doesn't affect redirects and is causing shellcheck to raise a flag. We can add the user to the microk8s group to avoid sudo but this requires a new session and would be complicated to add into the script considering we only use microk8s for the bootstrapping and then get rid of it.
@khalford
Copy link
Member

khalford commented Jan 8, 2026

@khalford Could you pick up the newgrp bit to complete this? I'll review and test both parts once that's done

Unfortunately newgrp starts a new shell and will be too complicated to add to the script than it's worth. I've changed it to use tee to fix the shellcheck problem. See my commmit for details.

@DavidFair DavidFair self-assigned this Jan 8, 2026
@khalford khalford merged commit bd557f8 into master Jan 9, 2026
1 check passed
@khalford khalford deleted the Fix_shellcheck branch January 9, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants