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
Is your feature request related to a problem? Please describe
It would nice to be able to pass variables from one zarf package to another within a uds-bundle whether they are expected ZARF_VARs or not.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I would like to use uds-core packages within my AWS EKS environments and configure components like loki to use AWS resources. The resources would need to be created prior to deploying uds-core and in most cases require outputs to be used as values inputs to the helm charts. What if the uds-core loki values do not expose ZARF_VARs needed to properly configure my deployment on AWS?
Ex.
I've created a zarf package that deploys S3 buckets, creates associated IRSA roles and policies, as well as defines the AWS Region I'm deploying to. Those outputs need to be passed along to the uds-core loki component's helm values. Each AWS environment I deploy to will/may have different values for each resource.
I can export these ZARF_VARs from my custom s3-irsa-iac zarf package within my uds-bundle and import them to the uds-core package but it's my understanding they are useless if the uds-core package is not expecting the same ZARF_VARs
Is your feature request related to a problem? Please describe
It would nice to be able to pass variables from one zarf package to another within a uds-bundle whether they are expected ZARF_VARs or not.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I would like to use uds-core packages within my AWS EKS environments and configure components like
loki
to use AWS resources. The resources would need to be created prior to deploying uds-core and in most cases require outputs to be used as values inputs to the helm charts. What if the uds-coreloki
values do not expose ZARF_VARs needed to properly configure my deployment on AWS?Ex.
I've created a zarf package that deploys S3 buckets, creates associated IRSA roles and policies, as well as defines the AWS Region I'm deploying to. Those outputs need to be passed along to the uds-core
loki
component's helm values. Each AWS environment I deploy to will/may have different values for each resource.I can export these ZARF_VARs from my custom s3-irsa-iac zarf package within my uds-bundle and import them to the uds-core package but it's my understanding they are useless if the uds-core package is not expecting the same ZARF_VARs
I
Describe the solution you'd like
It would be nice to have the ability to use those exported ZARF_VARs within the uds-bundle as regular VARs.
Ex.
Describe alternatives you've considered
Hardcoding the values I'm trying to override
(optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: