Usage command in README does not work
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- yaml
- Domain
- devops, documentation
Research direction
Open README and locate the usage command containing oc process and the appassessment-template.yaml URL. Update the command with --local=true and document the required OpenShift namespace admin privileges; verify the README reflects both the successful command and the permission limitation.
Written by the indexing model from the issue text.
Description
The following command given in the README does not work as intended:
oc process -f https://raw.githubusercontent.com/bcgov/AppAssessment/main/template/appassessment-template.yaml -p LICENSE_PLATE=<License Plate> -p CLUSTER_NAME="<Cluster Name>" -p APP_ASSESSMENT_IMAGE=image-registry.openshift-image-registry.svc:5000/bcgov/app-assessment | oc apply -f -
When used after filling in the correct parameters, the following error occurs:
error: unable to process template: the namespace of the provided object does not match the namespace sent on the request
error: no objects passed to apply
As noted in a RocketChat post, by adding the flag --local=true to the oc process part of the command, this issue is resolved. The fixed command looks as such:
oc process -f https://raw.githubusercontent.com/bcgov/AppAssessment/main/template/appassessment-template.yaml -p LICENSE_PLATE=<License Plate> -p CLUSTER_NAME="<Cluster Name>" -p APP_ASSESSMENT_IMAGE=image-registry.openshift-image-registry.svc:5000/bcgov/app-assessment --local=true | oc apply -f -
Additionally, it should be noted somewhere in the README that this requires admin privileges to the namespace in OpenShift, as if you try to run the fixed command without them, you get the following error after creating a few of the objects:
Error from server (Forbidden): error when retrieving current configuration of:
Resource: "rbac.authorization.k8s.io/v1, Resource=rolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=RoleBinding"
Name: "appassessment-view", Namespace: "<License Plate>-tools"
from server for: "STDIN": rolebindings.rbac.authorization.k8s.io "appassessment-view" is forbidden: User "<username>" cannot get resource "rolebindings" in API group "rbac.authorization.k8s.io" in the namespace "<License Plate>-tools"
I cannot create a PR for this as I do not have rights to publish to this repository, but I will leave it here for anyone trying to diagnose these issues in the future.
- Dominant language
- Python
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bcgov/AppAssessment
-
It's Been a While Since This Repository has Been UpdatedMay be free again @ShovelHand claimed this 1531 days ago, and no pull request is open. Open
bcgov/AppAssessment#40 · 3 comments · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
bcgov/AppAssessment#38 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
bcgov/AppAssessment#37 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
bcgov/AppAssessment#19 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
bcgov/AppAssessment#17 ·
All issues in bcgov/AppAssessment
Similar issues
-
README.zh-CN/ja/es still hard-code 501 test counts after README.md went count-freePossibly taken @Aaqibhafeezkhan claimed this today. Openbeginner documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BistaDinesh03/critique#164 · 1 comment ·
Maintainers usually reply within 1 day
-
bug IO
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MrNeRF/LichtFeld-Studio#3824 ·
Maintainers usually reply within 1 day
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-webui/open-webui#33200 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog checkPossibly taken @ocelotl claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
open-telemetry/opentelemetry-python#5825 ·
Maintainers usually reply within 2 days