-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[REGRESSION]: HelmDeploy@1 and HelmDeploy@0 stopped working with environment #20791
Comments
Hi @PAKalucki could you please share the successful and unsuccessful logs with debug set to true |
We faced the same issue with explicit connection configuration instead of environment configuration. Before we could just set the kubernetesServiceConnection attribute and it worked. Now the task asks for kubernetesCluster. Now it works like it is documented: HelmDeploy@0 - Package and deploy Helm charts v0 task
If connectionType is not specified, 'Azure Resource Manager' is default. If connectionType is 'Azure Resource Manager', the attribute kubernetesCluster is required. We just added connectionType: 'Kubernetes Service Connection' to our tasks. |
similar here, using HelmDeploy@0. Not affecting the environment but breaking behavior with requiring a new set of parameters to work like before. when it worked, the underlying version was
The usage in our case.
|
Hi @DRoppelt |
New issue checklist
Task name
HelmDeploy
Breaking task version
1.250.1
0.250.1
Last working task version
0.247.3
Regression Description
Both HelmDeploy@1 and HelmDeploy@0 started to ignore environment https://learn.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops#target-a-specific-environment-resource-from-a-deployment-job
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 22.04
Relevant log output
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
The text was updated successfully, but these errors were encountered: