-
Notifications
You must be signed in to change notification settings - Fork 173
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
Configure AppStreams via Activation Keys #8909
base: master
Are you sure you want to change the base?
Configure AppStreams via Activation Keys #8909
Conversation
👋 Hello! Thanks for contributing to our project. If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code. Reference tests: KNOWN ISSUES Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience. For more tips on troubleshooting, see the troubleshooting guide. Happy hacking! |
Suggested tests to cover this Pull Request
|
7035753
to
c79a0ea
Compare
web/html/src/manager/systems/activation-key/activation-keys-appstreams.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two small questions from the frontend side, looks good to go otherwise. 👍
c79a0ea
to
26d0e93
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @wweellddeerr, it's a very neat solution.
I've tested it successfully on my setup, and the code looks good as well.
There are still some things to do AFAICS:
- Unit tests where applicable (for ActivationKeyManager, utils.ts, etc.)
- API endpoints for the
activationkeys
namespaceaddAppStreams
removeAppStreams
- Include appstream info in
getDetails
- Test if the rest of the endpoints work together well (
clone
)
- Documentation updates for AKs (creating a separate issue will do)
Finally, it would be nice to have additional code comments in places where some complex logic is involved. Some parts especially in the TS domain took me some time to understand properly. When time passes, this will be even harder.
Since we're not in a rush to merge this, I think we can do all of the above with additional commits to this PR.
Hi @mcalmer, we can use another pair of eyes on the activation key logic ( |
@@ -136,11 +141,15 @@ public static void finishRegistration(MinionServer minion, Optional<ActivationKe | |||
// SSH Minions need this to set last booted value. | |||
statesToApply.add(ApplyStatesEventMessage.SYSTEM_INFO); | |||
} | |||
|
|||
handleActivationKeyAppStreams(activationKey, statesToApply, statesToApplyPillar); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is called at the wrong place.
The statesToApply
is a list which is executed in the order of the list.
With this order you might install packages from a stream you have not enabled yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. I'll fix that.
What does this PR change?
Add a new tab in activation key details page to pick AppStreams and enable the selected AppStreams on systems bootstrap.
GUI diff
Before:
After:
Documentation
No documentation needed: add explanation. This can't be used if there is a GUI diff
No documentation needed: only internal and user invisible changes
Documentation issue was created: Link for SUSE Manager contributors, Link for community contributors.
API documentation added: please review the Wiki page Writing Documentation for the API if you have any changes to API documentation.
(OPTIONAL) Documentation PR
DONE
Test coverage
No tests: add explanation
No tests: already covered
Unit tests were added
Cucumber tests were added
DONE
Links
Issue(s): https://github.com/SUSE/spacewalk/issues/24198
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test
(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:
Before you merge
Check How to branch and merge properly!