Hackathon subscription activation and registry service account implementation

[dgolovin]

No description provided.

[benoitf]

I have a question around all generated classes

if they're automatically generated, should we avoid to store them into the git registry and generate them as part of a npm task ?

[dgolovin]

@benoitf we can definitely do that, but they not going to change much and also would be good to have generated sources tagged as everything else.

Another option is to have npm package per API so other projects, like OpenShift Toolkit, can use it too.

[benoitf]

I think that your suggestion with another repository with only the generated classes would be the best option.

• it avoids to include generated stuff in this extension (as users/developers might be tempted to tweak some classes for their needs)
• it allows to reuse the model in different locations and lifecycle here is specific to the model change
• we never commit generated objects in the repository (in this 3rd party repository), only the model, tooling/scripts to generate it so again there is no risk to have manual edits

[vrothberg]

@benoitf @dgolovin can you give some pointers on how I can test this code? I am blank on the toolchain.

[benoitf]

@vrothberg I would say that there are like 2 ways

1. Development mode:

assuming you're able to build podman desktop locally
https://github.com/containers/podman-desktop/blob/main/CONTRIBUTING.md#prerequisites-prepare-your-environment

you clone https://github.com/containers/podman-desktop/ and https://github.com/redhat-developer/podman-desktop-redhat-account-ext

then run yarn inside podman-desktop folder and in podman-desktop-redhat-account-ext

then from podman-desktop-folder you do

yarn watch --extension-folder ../podman-desktop-redhat-account-ext

2. build mode

you fetch a binary of podman desktop

you clone this pull request and build the image and publish it somewhere
(can use instructions from CI https://github.com/redhat-developer/podman-desktop-redhat-account-ext/blob/main/.github/workflows/ci.yaml#L52-L60
)

then in Settings/extensions you put the path to the OCI image (need to be a remote one) and then it'll install the extension

(this repository has no CI where it's publishing automatically PRs to some OCI registries)

[vrothberg]

Thanks a lot, @benoitf ! The instruction were very helpful.

[vrothberg]

Nothing to worry about right now but something to improve later on: the service-account user names can be very long as seen on the screenshot below. Maybe we can truncate them?

[benoitf]

@vrothberg if you can file an enhancement request at https://github.com/containers/podman-desktop/issues/new?assignees=&labels=kind%2Fenhancement+%E2%9C%A8&projects=&template=enhancement.yml

[vrothberg]

Thanks! Opened podman-desktop/podman-desktop#5670

[vrothberg]

One more thing I noticed while playing:

The Authentication page displayed "LOGGED OUT" after restarting Podman Desktop. However, we're still logged into the registry and subscription-manager is still working inside the VM (even after reboots). So we need to flesh out what "logged in" and what "logged out" means.

[vrothberg]

Is this ready to merge? Then we can cut an alpha release and incrementally improve.

[benoitf]

I think all github workflows, dependency updates, tsconfig changes could be separated small PR as they're not related to the changes

[dgolovin]

Closed in favor of 0.0.2-alpah.x branch PR #34