You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First - it's not clear what is needed as far as codefresh token scopes. Is the idea to do trial and error to discover what is needed? That would be odd, but it seems to be the case....
Also tool does not check permissions and fails during the run? Is there is a reason for doing that vs checking for scopes in the beginning? Explaining what scopes would be actually ideal. And it would be even better to generate any token that it needs itself, while validating - say like gcloud does it.
Finally the issue. It seems that tool fails along the way with the following message:
"Codefresh envrionment name is required"
codefresh.io (main*) » codefresh runner init
Previous installation state:
✓ run cluster acceptance tests
✓ generate new agent name
✓ create new agent
✓ install new agent
✓ generate new runtime name
✓ create new runtime
⤳ update runtime environment images with docker-registry url
✓ update runtime environment with env vars and resources
✓ set new runtime as default
✓ add cluster integration
✘ install runtime
◼ install app-proxy
◼ update runtime environment app proxy ip
◼ update agent with new runtime
◼ attach runtime to agent
◼ install cluster monitoring
◼ generate helm value files
◼ create test pipeline
◼ execute test pipeline
? Detected previous incomplete installation, do you want to resume this installation? Yes
Installation options summary:
1. Kubernetes Context: dev
2. Kubernetes Namespace: codefresh
3. Set this as default account runtime-environment: true
4. Execute demo pipeline after install: true
5. HTTP proxy: none
6. HTTPS proxy: none
7. No proxy: none
executing step: install runtime
Error: Codefresh envrionment name is required
Error: Failed to install runtime: Component exited with status code 1
It's not clear what really is the issue and what I should do about it? Or maybe it's just a bug in the tool?
The text was updated successfully, but these errors were encountered:
Two issues really.
First - it's not clear what is needed as far as codefresh token scopes. Is the idea to do trial and error to discover what is needed? That would be odd, but it seems to be the case....
Also tool does not check permissions and fails during the run? Is there is a reason for doing that vs checking for scopes in the beginning? Explaining what scopes would be actually ideal. And it would be even better to generate any token that it needs itself, while validating - say like gcloud does it.
Finally the issue. It seems that tool fails along the way with the following message:
"Codefresh envrionment name is required"
codefresh.io (main*) » codefresh runner init
Previous installation state:
✓ run cluster acceptance tests
✓ generate new agent name
✓ create new agent
✓ install new agent
✓ generate new runtime name
✓ create new runtime
⤳ update runtime environment images with docker-registry url
✓ update runtime environment with env vars and resources
✓ set new runtime as default
✓ add cluster integration
✘ install runtime
◼ install app-proxy
◼ update runtime environment app proxy ip
◼ update agent with new runtime
◼ attach runtime to agent
◼ install cluster monitoring
◼ generate helm value files
◼ create test pipeline
◼ execute test pipeline
? Detected previous incomplete installation, do you want to resume this installation? Yes
Installation options summary:
1. Kubernetes Context: dev
2. Kubernetes Namespace: codefresh
3. Set this as default account runtime-environment: true
4. Execute demo pipeline after install: true
5. HTTP proxy: none
6. HTTPS proxy: none
7. No proxy: none
executing step: install runtime
Error: Codefresh envrionment name is required
Error: Failed to install runtime: Component exited with status code 1
It's not clear what really is the issue and what I should do about it? Or maybe it's just a bug in the tool?
The text was updated successfully, but these errors were encountered: