support for additional variables from connectors
pending feedback
S
Silver Grasshopper
I want to use the URL from a connector. For ex, I have a non-prod and prod connector at account level, and want to use the URL as a variable from that, instead of having to create an account level variable for the URL.
Log In
E
Electronic Emu
We need to build a custom step template (using plugin or shell script step).
The step should run as part of CD stage (in the context of Harness Lambda service, Harness environment)
The step uses AWS CLI to make some changes and publish AWS lamdba version.
The step needs AWS credentials to invoke aws lambda cli. Since we already have a AWS connector in the Harness project (that is used for AWS Lambda deployments), we want to use the connector in the step. We do not want to provision AWS access key pair. The AWS connector has IRSA/Cross account role configured. The AWS CLI in the custom step should assume the role configured in Connector's Cross account role to make AWS Lambda changes.
Rohan Gupta
Merged in a post:
Connector Expressions - Support IRSA
A
Agreed Harrier
We have utilized connectors in our AWS Space, and while we can attain
<+infra.variables.AWSSpace.spec.credential.spec.accessKey>
and get secrets for <+infra.variables.AWSSpace.spec.credential.spec.secretKeyRef.identifier>
We cannot do so when utilizing IRSA, only when using other Connector configuration methods.
We need a method to support the same functions when IRSA is involved, and we also need to be able to attain the information about a session ID to keep our processes going.
Canny AI
Merged in a post:
In SMP URL can be optionally passed for aws connector
A
Agate Thrush
Please provide a option where a URL can be optionally passed for aws connector.
Rohan Gupta
Merged in a post:
Fetch Connector Details via Variable Expressions
A
Accurate Pigeon
As a user, I would like the ability to dynamically fetch connector details using variable expressions within Harness, allowing these values to be accessible in shell script steps without needing to hardcode them.
Hardcoding these values can lead to challenges in managing and updating configurations, particularly when connector details change frequently.
Prateek Mittal
pending feedback
Prateek Mittal
under review
Prateek Mittal
Hi Justin,
Can you please expand the use case? Do you want to refer one connector to another connector?
Thanks,
Prateek