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

[WIP] cockpit create blueprint #2780

Draft
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

kingsleyzissou
Copy link
Collaborator

This is still a work in progress for creating a blueprint from the CreateImageWizard.

kingsleyzissou and others added 11 commits January 23, 2025 14:11
The browser router doesn't seem to work inside cockpit, switching
to the hashrouter resolves this.
Switch the useFlag usage to the stub function defined in the
`useGetEnvironment` utility
We need to check for the on-prem use case
We were making a call to a dead endpoint to get the architectures.
Instead, create a custom query function to return the list of architectures
and image types.
Create a get blueprint endpoint for the on-prem store.
Create the boilerplate function for getting the Oscap profiles. We will
need to make a call to the `oscap` binary to get this information. So
we will leave it empty for now.
Create a helper hook for RTK prefetch queries. This wrapper function
is needed since the imagebuilderApi and cockpitApi aren't at parity
yet.
Currently, the wizard still needs some of the other stores. If we
omit them, the wizard fails to launch
Including an image in the on prem version inside cockpit is not
trivial. We need a bit of a workaround to get the various target icons
showing on the on-prem version in cockpit.
For a start, we will disable custom repositories and the OpenSCAP steps
for the on-prem version of the frontend.
Add a hook that gets the host distro for the on-prem frontend. If there
is an issue we will fallback to the default. For the service we also
just use the default distro.
Add a stub function for the `os-release` package from cockpit.
We can ignore the org-id when trying to get the state of the
blueprint during the blueprint creation. This is unnecessary
info for `on-prem`
This is not ideal, but we needed to add an empty endpoint for
this, even though we're ignoring it on prem. The frontend for
the service makes the api call regardless, so we can't ignore
this.
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 this pull request may close these issues.

1 participant