Feature Requests

Anonymous

Feature Requests for Harness. Select 'Category' based on the module you are requesting the feature for.
Implement support to skip or disable clone_workspace_repo in IACMTerraformPlugin
Pipeline Runtime Optimization for ECS IACM Stages Using Custom Image We are evaluating pipeline runtime optimization for ECS IACM stages with our own terraformer image that has Terraform (provisioner version aligned with workspaces, e.g. 1.0.11) The Terraform module tree and any other dependencies. Provider plugins required for the terraformer modules to run(e.g. hashicorp/aws, hashicorp/null, etc..) by preinitializing the modules during the image build process. What we need: Allow us to skip/disable clone_workspace_repo & init step in the IACMTerraformPlugin and let us supply explicit inputs at runtime: Run Terraform with module_path pointing to the terraform module that is already there in our custom image and pass tfvars_path from cloudos-deployment-files repo (pinned by TF_VALUES_GIT_SHA), similar to our cos-tf / CD Terraform Plugin pattern. What is the benefit: This would reduce IACM stage execution time with the Pre baked image by skipping module repos clone on every exec. This would reduce the API throttling issue that we are encountaring with git requests. We often noticed our artifactory system is flaky. If we can use the prebaked image, then it would also eliminate the requests to external dependencies like artifactory system to download the providers on every IACM step execution. Support ticket opened - https://harnesssupport.zendesk.com/agent/tickets/133316 Tested with custom image in the awsInfo step in this pipeline execution & i noticed the git clone is not skippable in the current state - https://autodesk-sb.harness.io/ng/account/l_afiWBSQkuGVNUS6I4YsA/all/orgs/cloudos_deploy/projects/wonkaecs/pipelines/wonkaecs_ecs_stg_st/executions/RaMN9DseR_SfMwhy182fyA/pipeline?stage=5SXyZeoPTI-LY0xy8aanZw&stageExecId=HH2mGPDWRgSgrAUiA8cc0A
0
·
IACM
IaCM: Honor GIT_SSH_FIPS_KEX_ALGORITHMS in native Terraform init (git modules)
Support threads - https://harnesssupport.zendesk.com/agent/tickets/126199 https://harnesssupport.zendesk.com/agent/tickets/132475 Context ------- We run Terraform via IaCM on GovCloud/FIPS Kubernetes workers (FIPS OpenSSH, e.g. platform validation nodepools). Pipelines use private Git module sources, e.g. git:: git@git.autodesk.com :... Problem ------- IACMTerraformPlugin step "init" fails during module download (git clone/fetch). Typical error: "c25519 is not allowed in FIPS mode" (or similar FIPS/SSH KEX failures). We set FIPS-related env on the IaCM init step (e.g. GIT_SSH_FIPS_KEX_ALGORITHMS, AWS_USE_FIPS_ENDPOINT). GIT_SSH_FIPS_* on IACMTerraformPlugin does not appear to reach the git subprocess the way it does in our working CD/cos-tf Plugin init path. Initial test ------------ Failing path: IACMTerraformPlugin init with git::git@... modules on FIPS nodes. Working path: Plugin (cos-tf) terraform init with DRONE_SSH_KEY, DRONE_NETRC_MACHINE, GIT_SSH_FIPS_KEX_ALGORITHMS, TF_CLI_ARGS_init=-backend=false (same module sources). Root cause (observed) --------------------- Parity gap: on FIPS OpenSSH, git must use FIPS-allowable KEX/host algorithms. cos-tf Plugin wires SSH/deploy key + FIPS KEX correctly; native IaCM init still invokes git with defaults that can pick curve25519. Interim workaround (not acceptable long-term) --------------------------------------------- Prefetch modules with Plugin init, then IACMTerraformPlugin init with TF_CLI_ARGS_init=-get=false, plus workspace permission fixes (root prefetch vs non-root IaCM). This is fragile (two-step init, cache drift, DRONE_* coupling, easy to miss in new pipelines). Requested feature / fix ----------------------- IACMTerraformPlugin init: apply FIPS-safe Git/SSH for all git subprocesses used for module download (honor GIT_SSH_FIPS_KEX_ALGORITHMS and/or documented equivalent; parity with CD Terraform Plugin / SSH modules).
0
·
IACM
Load More
→