Porchctl command fixes:

[dimitar-axyomcore]

Fixes for porchctl repo commands described in nephio-project/nephio#755 issue.

• repo get: Output n=Namespace column when -A/--all flag specified.
• repo reg: Use kubeconfig context namespace if -n/--namespace flag not provided.
• repo unreg: Use kubeconfig context namespace if -n/--namespace flag not provided.

I've resubmitted this PR under new GH account to be able to sign the corporate CDL.

I would need guidance on how to approach tests for the commands. I've noticed the repo reg command uses a fake porch server to handle the tests cases. Should I follow suit for commands affected by this PR?

[nephio-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dimitar-axyomcore
Once this PR has been reviewed and has the lgtm label, please assign tliron for approval by writing /assign @tliron in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

• ❌ The email address for the commit (0f4dcc1) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[nephio-prow]

Hi @dimitar-axyomcore. Thanks for your PR.

I'm waiting for a nephio-project member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dimitar-axyomcore]

I am currently working on signing the Corporate CLA

[liamfallon]

/ok-to-test

[dimitar-axyomcore]

At this point I am not sure if the corporate Easy CLA will be signed. Please feel free to assign this issue to someone else.
I really appreciate you were waiting for that long :-)

[dimitar-axyomcore]

Hi @efiacor ,

I made one more effort to sign the corporate CLA. Please give me a few more days and hopefully I could start working on the PR next week.

[dgeorgievski]

Hi @efiacor ,

I made one more effort to sign the corporate CLA. Please give me a few more days and hopefully I could start working on the PR next week.

it looks like my company is not ready for contributing to Open Source projects, yet. Just to give some context, Axyom.Core was spun off Casa Systems last May and our current priorities don't have room for this task.

We have two options. Either I re-open the initial PR opened under my personal GitHub account or you guys complete it. I know the PR has been opened for quite some time now.

In any case, thanks for waiting on my response.